You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the following steps to install nvidia-docker v2 (very hacky though):
install nvidia driver
instead of the volume I simply copy the files to the host, e.g.
/usr/bin/docker run --rm --volume /opt/nvidia/current:/output srcd/coreos-nvidia:${VERSION} cp -a /opt/nvidia/. /output/
install libnvidia-container
(build and) install nvidia-container-runtime
create small bash scripts in /run/torcx/bin for nvidia-container{-runtime,-runtime-hook,-cli} to make sure they are accessible by docker and libraries are in LD_LIBRARY_PATH
create /etc/docker/daemon.json and set default runtime to nvidia
restart docker
add the nvidia-docker bash scripts
There is only one issue currently: The nvidia-container-runtime somehow (even though same commit as installed runc) has a regression. And fails to run containers with docker run --security-opt=no-new-privileges (coreos/bugs#1796).
@lsjostro I would be interested in having your previous "nvidia-docker v2 + coreos" version, even if not cleaned up and production-ready: nvidia-docker v2 enables sharing GPUs between containers (at the cost of losing k8s scheduling) that device drivers solutions don't support (and won't for the foreseeable future).
Activity
rporres commentedon Nov 24, 2017
Above links are broken. I guess it's because
2.0branch was merged into master recently by means of NVIDIA/nvidia-docker@fe18749thomas-riccardi commentedon Nov 24, 2017
@rporres indeed, I updated my comment.
mcuadros commentedon Dec 22, 2017
Its requires any changes? The current version was done for bare docker, not even nvidia-docker 1.0
thomas-riccardi commentedon Dec 22, 2017
using nvidia-docker v2 would simplify the
docker runpart: no need to add:So what change is required is in fact installing nvidia-docker v2 in coreos, and removing the
nvidia-drivercontainer.trevex commentedon Jan 29, 2018
I used the following steps to install nvidia-docker v2 (very hacky though):
/run/torcx/binfornvidia-container{-runtime,-runtime-hook,-cli}to make sure they are accessible by docker and libraries are inLD_LIBRARY_PATH/etc/docker/daemon.jsonand set default runtime to nvidianvidia-dockerbash scriptsThere is only one issue currently: The
nvidia-container-runtimesomehow (even though same commit as installed runc) has a regression. And fails to run containers withdocker run --security-opt=no-new-privileges(coreos/bugs#1796).lsjostro commentedon Feb 2, 2018
We have it working as well (nvidia-docker v2 + coreos + k8s device plugin). We will try to clean it up and hopefully be able to share it soonish.
lsjostro commentedon Feb 9, 2018
went for this instead
GoogleCloudPlatform/container-engine-accelerators#54
thomas-riccardi commentedon Feb 9, 2018
@lsjostro I would be interested in having your previous "nvidia-docker v2 + coreos" version, even if not cleaned up and production-ready: nvidia-docker v2 enables sharing GPUs between containers (at the cost of losing k8s scheduling) that device drivers solutions don't support (and won't for the foreseeable future).
In any case, GoogleCloudPlatform/container-engine-accelerators#54 is useful too, thanks for that !