Package Details: nvidia-docker 2.2.2-1

Git Clone URL: https://aur.archlinux.org/nvidia-docker.git (read-only)
Package Base: nvidia-docker
Description: Build and run Docker containers leveraging NVIDIA GPUs
Upstream URL: https://github.com/NVIDIA/nvidia-docker
Keywords: cuda docker gpu nvidia
Licenses: BSD
Submitter: marcelhuber
Maintainer: jshap (kiendang)
Last Packager: jshap
Votes: 34
Popularity: 0.21
First Submitted: 2016-07-26 09:17
Last Updated: 2019-09-09 17:21

Pinned Comments

jshap commented on 2019-08-17 01:14

This package is now deprecated in upstream, as you can now use nvidia-container-toolkit together with docker 19.03's new native GPU support in order to use NVIDIA accelerated docker containers without requiring nvidia-docker. I'm keeping the package alive for now because it still works but in the future it may become fully unsupported in upstream.

For more info, see: https://wiki.archlinux.org/index.php/Docker#Run_GPU_accelerated_Docker_containers_with_NVIDIA_GPUs

Latest Comments

« First ‹ Previous 1 2 3 Next › Last »

eschwartz commented on 2018-05-23 23:05

Also this is no longer an arch-dependent package, it's an any package.

eschwartz commented on 2018-05-23 18:14

Please package this properly, using original sources instead of rpms.

There's no reason to use some prebuilt rpm just to cp these files:

https://github.com/NVIDIA/nvidia-docker/blob/master/nvidia-docker https://github.com/NVIDIA/nvidia-docker/blob/master/daemon.json https://github.com/NVIDIA/nvidia-docker/blob/master/LICENSE

rpm spec which cp's those files: https://github.com/NVIDIA/nvidia-docker/blob/master/rpm/SPECS/nvidia-docker2.spec

vfbsilva commented on 2018-05-09 23:33

Problems to run here:

nvidia-docker run --rm nvidia/cuda nvidia-smi

docker: Error response from daemon: create nvidia_driver_396.24:

VolumeDriver.Create: internal error, check logs for details. See 'docker run --help

lukeyeager commented on 2018-04-12 20:07

@whenov got it, thanks for the context. For now, I'm going to leave the packages as they are. For one reason, each package has it's own version number upstream, and I feel like it's useful to see that in my local package list.

If others agree that they'd prefer a single package, please chime in!

whenov commented on 2018-03-16 01:53

@lukeyeager, it's just that these dependency packages are unlikely to be the dependencies of any other packages. And for those who prefer to use AUR manually with makepkg, it's more convenient to have a single package.

lukeyeager commented on 2018-03-15 16:29

@whenov That's definitely possible. I was just following the upstream packaging convention. What's the upside of having a single package?

I'm also happy to let this package die and let the nvidia-docker v1 package maintainer take over. I haven't found time this week to update all the out-of-date dependencies of this package anyway.

whenov commented on 2018-03-15 16:05

Is it possible to merge nvidia-docker2 and its four dependencies into a single package?

mimoralea commented on 2017-08-23 13:17

@simon_sjw, your solution works nicely. Thanks for sharing.

simon_sjw commented on 2017-08-07 00:28

On installing, I had a fail on testing using
nvidia-docker run --rm nvidia/cuda nvidia-smi
getting an "invalid cross-device link" error.
(When this is running correctly, you should get the status of your gpu as seen from within docker.)

To fix:
Use systemctl status nvidia-docker to tell you location of the service.
Then open it with your favourite editor and alter
ExecStart=/usr/bin/nvidia-docker-plugin -s $SOCK_DIR
to
ExecStart=/usr/bin/nvidia-docker-plugin -s $SOCK_DIR -d /usr/local/nvidia-driver
the -d flag allows you to ensure that the NVIDIA driver installation lives on the same partition as the volume directory of the Docker plugin. (this is a known issue with nvidia-docker).
https://github.com/NVIDIA/nvidia-docker/issues/216
and
https://github.com/NVIDIA/nvidia-docker/wiki/nvidia-docker-plugin#known-limitations
After making this change, remember to stop, reload and start the service (or just reboot your machine).

marcelhuber commented on 2017-02-24 09:56

@xoryouyou: Thank you for adapting the corresponding lines.