Open lgorenstein opened 3 years ago
Our actual implementation for downloading containers from NGC makes use of the Docker SDK, which makes use of a connection to the host's docker daemon. So this workflow does rely on a functional Docker daemon.
We'd be open to removing this dependency, but we don't have any plans to work on this right now.
Thank you Adam, looking forward to this! I mean, even a '--no-docker-daemon' plug would work for my use case :)
This is a show stopper for me at my company. Looks like we are going to have create our own tool. Sad no one is addressing this.
I tried to convert the replicator into a Singularity image to be able to use it on a Docker-less cluster:
This worked just fine and generated a
replicator_201015.sif
. Then off to replicating (note: neededPYTHONNOUSERSITE=1
otherwise stuff from~/.local/lib/python3.6
was getting in the way... I might suggest defining this variable in the container proactively):Unfortunately, the run crashes citing the lack of Docker daemon:
From a naive user prospective, if I run from singularity (i.e. outside of Docker ecosystem) and all I want is to dump a bunch of image files, I should not be needing a functional Docker daemon on the host, right? Would it be possible for the replicator to detect such condition?