-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does minikube support AMD GPUs #19463
Comments
@yx-lamini we dont have support tfor amd GPUs but I would be happy to accept a contribution to add it |
Could you briefly explain or point to docs/code-files for Minikube's high-level logical architecture for supporting NVIDIA GPUs? Or provide suggestions on how we could support AMD GPUs in Minikube? I'd love to contribute. We actually are actively assess the technical investment for making minikube support AMD GPUs.
I think that's through the container device interface (CDI). Assuming we build on top of docker's CDI to support AMD GPUs in Minikube, what's the suggested approach we should be taking with Minikube? Better yet, if minikube's Nvidia support |
minikube uses the docker's --gpus all to attach the gpu to the container, and we also install the nvidia-smi in the base image is the required for it...so I am wondering if we need to install same driver for amd ? do you have an example of running gpu workload in a nested container ? (inside the docker container) that would be cool if we can have support for amd as well. and I am assuming you are talking about dedicated AMD gpus, right? |
btw here is an example of nvidia workload #19486 |
Great, I'll take a look
rocm/pytorch is the one we use.
We use AMD GPUs in a data center cluster setting. GPUs are shared among kubernetes pods Does this align with what you mentioned as "dedicated"? |
What Happened?
Does not seem work with AMD GPUs. Complains
docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]]
Attach the log file
N/A
Operating System
Ubuntu
Driver
Docker
The text was updated successfully, but these errors were encountered: