-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
nvidia-docker error: "ldconfig failed with error code: 1: unknown" #173953
Comments
I have a similar issue, unsure if it's related; I'm using I can run an nvidia container with the nvidia runtime:
but I cannot do so if uids are mapped in a different way:
Regarding docker itself, I can also reproduce the error using the
but I can run
I hope it helps.
|
Are there any workarounds to this? I can use the ubuntu NVIDIA containers, but I cannot run a nix docker container built with
|
The only workaround I was able to do was using the NVIDIA ubuntu docker images as a base image.
|
This only applies if you're trying to access your gpu in the "old" way. With CDI, you should run your image with:
if you're using nixos, you can enable support for this with |
Describe the bug
nvidia-docker fails to run any image.
Steps To Reproduce
virtualisation.docker = { enable = true; enableNvidia = true; } in system
configuration.nix`sudo -g docker docker run -it --rm hello-world
If not, you may need to set
virtualisation.docker.storageDriver
explicitly, depending on your filesystem setup.sudo -g docker docker run --privileged --gpus all -it --rm hello-world
Expected behavior
For docker to run the
hello-world
container in privileged mode with host GPUs exposed.Additional context
This appears to be at least partly an upstream bug, going by some issue reports I found.
I cannot tell whether the NixOS package/module simply needs to be updated, or whether there is NixOS-specific work that needs to be done in upstream.
Notify maintainers
virtualisation.docker.enableNvidia
option)nvidia-docker
maintainer)Metadata
The text was updated successfully, but these errors were encountered: