Only works once #34
Comments
Yes this is one of our limitations documented here A workaround would be to change |
I'm actually a little bit of a fan of the data container idea.
I was already playing with this idea when you mentioned it, it seems to work well to me :) I used a Makefile with
And a Dockerfile_nvidia_driver of
Sorry it's a little messy, but it was just a quick poc to prove to myself it would work |
Data containers and volumes are exactly the same thing under the hood. Using volumes directly makes more sense because that's where Docker is headed with persistent volumes and the new Creating an image and a container for the sake of having a volume referenced is not ideal. Besides, you still have to make sure that the container is not deleted. This, really is a Docker issue and will be fixed upstream eventually. In the meantime I suggest you run your container without volume="$(sudo nvidia-docker volume setup)"
nvidia-docker create --name=LOCK -v $volume:/data:ro tianon/true nvidia-docker run --rm nvidia/cuda nvidia-smi
nvidia-docker run --rm nvidia/cuda nvidia-smi Regarding copy vs hardlink, we chose to do so to keep the ecosystem as light as possible. Copying around MB of driver files in order to launch a container is not an option. |
Closing since it's an issue with upstream Docker. |
Fixed in Docker 1.10, the documentation has been updated. |
Just a notice, I've run the install instruction from README and tried to test, it failed with error:
The solution was:
Installed version: |
Are you running Ubuntu? If so, can you show me the output of:
|
hi @3XX0, similar problem as @orian.
and when I test it,
it give the the error (which take me to this issue)
My
|
I had this error after upgrading my nvida-driver to the latest version (wanted to use cuda 8): ^[[Adocker: Error response from daemon: create nvidia_driver_367.44: create nvidia_driver_367.44: Error looking up volume plugin nvidia-docker: plugin not found. Running on centos 7.
fixed my issues |
Running on AWS ami linux using nvidia-docker fails to initially launch container nvidia/cuda:7.5-devel nvidia-docker run --rm nvidia/cuda:7.5-devel nvidia-smi
Then when I try to launch the container again it succeeds. Currently using docker version 1.11.2, build b9f10c9/1.11.2
|
I'm not very familiar with
docker volume
, but it appears to be ONLY good for one use.sudo ./nvidia-docker volume setup
docker volume ls
./nvidia-docker run --rm nvidia/cuda nvidia-smi
./nvidia-docker run --rm nvidia/cuda nvidia-smi
docker volume ls
Tested on Ubuntu 14.04 running Docker 1.91 and Centos 7 running docker 1.9.0
It just seems like if
sudo nvidia-docker volume setup
is in the "Initial setup" section, than it shouldn't need to be run every time I create a new container, or am I missing something?The text was updated successfully, but these errors were encountered: