-
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
Where to get minikube v1.32.0-beta0 or instructions to run minikube with gpu suport #17380
Comments
Hi @rafariossaa, we don't have the beta release out yet, but if you want to use the GPU feature now you can download the binary built in the PR. https://storage.googleapis.com/minikube-builds/17314/minikube-linux-amd64 |
Thanks, I will give it a try and provide feedback. |
Hi,
|
Thanks for the feedback, glad to hear that it's working for you! We anticipate releasing the beta on Thursday, I'll close this issue once the release is out |
Hi, The issue I found is when restarting minikube: $ minikube start --driver docker --container-runtime docker --gpus all --cpus=8 --memory=8G
😄 minikube v1.31.2 on Ubuntu 23.04
✨ Using the docker driver based on user configuration
📌 Using Docker driver with root privileges
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🔥 Creating docker container (CPUs=8, Memory=8192MB) ...
❗ Using GPUs with the Docker driver is experimental, if you experience any issues please report them at: https://github.com/kubernetes/minikube/issues/new/choose
🛠 Installing the NVIDIA Container Toolkit...
🐳 Preparing Kubernetes v1.28.2 on Docker 24.0.6 ...
▪ Generating certificates and keys ...
▪ Booting up control plane ...
▪ Configuring RBAC rules ...
🔗 Configuring bridge CNI (Container Networking Interface) ...
▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
▪ Using image nvcr.io/nvidia/k8s-device-plugin:v0.14.1
🔎 Verifying Kubernetes components...
🌟 Enabled addons: storage-provisioner, nvidia-device-plugin, default-storageclass
🏄 Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
$ minikube stop
✋ Stopping node "minikube" ...
🛑 Powering off "minikube" via SSH ...
🛑 1 node stopped.
$ minikube start --driver docker --container-runtime docker --gpus all --cpus=8 --memory=8G
😄 minikube v1.31.2 on Ubuntu 23.04
✨ Using the docker driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🚜 Pulling base image ...
🔄 Restarting existing docker container for "minikube" ...
❗ Using GPUs with the Docker driver is experimental, if you experience any issues please report them at: https://github.com/kubernetes/minikube/issues/new/choose
🛠 Installing the NVIDIA Container Toolkit...
❌ Exiting due to RUNTIME_ENABLE: Failed to enable container runtime: failed installing the NVIDIA Container Toolkit: /bin/bash -c "curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg": Process exited with status 2
stdout:
stderr:
gpg: cannot open '/dev/tty': No such device or address
curl: (23) Failed writing body
╭───────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ 😿 If the above advice does not help, please let us know: │
│ 👉 https://github.com/kubernetes/minikube/issues/new/choose │
│ │
│ Please run `minikube logs --file=logs.txt` and attach logs.txt to the GitHub issue. │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────╯ In the last step, it happens the same if I just run |
Please make a new issue, I'll experiment with this myself as well. |
I have created #17405 |
@spowelljr its will be nice also to include the link somewhere on documentation page here https://minikube.sigs.k8s.io/docs/tutorials/nvidia/ thanks |
Hi @spowelljr, |
Hi @wings2020 , |
Hi @rafariossaa , However, my env is air gap network, not sure about that command: |
I've been following this topic closely. It would be amazing to test out a new beta to see if it's working :D |
@wings2020 @rafariossaa I think I found where the newer files are stored. The builds corresponding to #17488 which implement the fix for #17405 can be found with the following prefix: https://storage.googleapis.com/minikube-builds/17488/minikube-linux-amd64 I noticed that the number seems to match the PR number on GitHub, so I went with that. |
Sorry for the delay, the release PR is up, just waiting for the tests to come back, if all is good it will be out today. As @kdmkone said above, https://storage.googleapis.com/minikube-builds/17488/minikube-linux-amd64 would be the binary with the fix for the problem outlined in this issue. As per @wings2020 concern about an air gapped system, the |
@wings2020 Here's a PR for what I talked about above, I'll link you the binary to try yourself once it's built |
Thanks you all. |
Since the release is out I'm going to close this issue |
@wings2020 You can use the link below and it should work on your air gapped machine https://storage.googleapis.com/minikube-builds/17516/minikube-linux-amd64 |
@spowelljr thank you very much!! It works for me now :)) |
What Happened?
Hi,
I am trying to run minikube with gpu (nvidia) support.
I this doc link it is indicated that I need minikube v1.32.0-beta0, but I can not find it in the releases link, the latest beta version I found was
v1.26.0-beta.1
.In the case that
v1.32.0-beta0
is not available, could you provide instructions to run minikube with docker driver and enabling gpus ?I currently can run containers on docker that use gpu:
Thanks forehand.
Attach the log file
--
Operating System
Ubuntu
Driver
Docker
The text was updated successfully, but these errors were encountered: