-
Notifications
You must be signed in to change notification settings - Fork 204
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
3.3.0.115 docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]]. #173
Comments
I think starting with this commit, we start to try to run the container with GPU access. Perhaps you could try to modify the script locally by removing those lines and see if works? |
@kngharv This NVIDIA/nvidia-docker#1243 may help you. |
Managed to resolve this by installing nvidia-container-toolkit, as described in NVIDIA/nvidia-docker#1243 (comment)_
|
In my case, I can access the GPU from docker container right after a fresh install.
|
I am running Arch, with KDE of 5.25.2. When I run
Then I tried removing those 3 lines that @sefeng211 mentioned, but it didn't work. Can anyone help? Thanks in advance! |
I have the same issue. Rebooting makes the issue appear again. Have you been able to solve that? |
@Jiawens @frankmanbb Have you tried to install |
I had installed Anyway, thanks for your and @qinenergy's advice. |
I have the same question,but after installing "nvidia-container-toolkit" ,it report an error as
|
I have this issue on Ubuntu 22.04 too, any update please? |
It does not work for me.
|
I received the same error here: docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: initialization error: load library failed: libnvidia-ml.so.1: cannot open shared object file: no such file or directory: unknown. After searching, I discovered that I did not install any Nvidia driver on the computer because I thought my laptop didn't have Nvidia graphic cards. Running this solved all the issues: sudo apt-get install cuda |
I can't even get the container started.
Yet, I am not even sure this is a bug.
I am running Ubuntu/20.04.
I am running Wayland instead of X.
I am running nouveau driver instead of nvdia driver.
In addition, I am running a displaylink driver for my usb hub and two external screens.
So, my question of the day are:
Or, it is something else that broke my container? I am not ruling out that I am the one which is broken.
thanks in advance
The text was updated successfully, but these errors were encountered: