Arvados

(11:27:22 AM) bcosc: my guess for 8103 is that you need to arv keep docker them into the projects
(11:27:40 AM) bcosc: arv keep docker will give the docker metadata to the projects where as copying them just puts the tar file
(11:27:54 AM) sguthrie: bcosc, how do I arv keep docker them into a project?
(11:29:06 AM) bcosc: arv keep docker --project-uuid [uuid] [image name]
(11:29:27 AM) sguthrie: ok. I need to do this for every image name?
(11:29:30 AM) bcosc: yep
(11:29:37 AM) sguthrie: and is the project-uuid the destination or source?
(11:29:45 AM) bcosc: destination

This would probably work, but docker was not available on the shell node the user was using (when accessed via the web shell)

julianaalverio@shell:~$ groups
julianaalverio fuse docker
julianaalverio@shell:~$ arv keep docker sguthrie/numpy
arv-keepdocker: no matching image found
julianaalverio@shell:~$ arv keep docker sguthrie/numpy:latest
arv-keepdocker: no matching image found

Need to find the Docker metadata links for these images, and move them to the same project as the Docker image(s) themselves.

Julian, Only the person creating/setting up the Docker image needs to follow the steps in Sally's comment. Now that they're done, it should be possible to run the pipeline. You don't need to run them yourself.