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
You should be able to directly download the images hosted by galaxy, but I agree to get the singularity conversion of the dockerhub images you do need Singularity.
Maybe it should be added in the docs, I'm thinking that most people that download for offline usage have (or at least should have) singularity installed on a system that can communicate with their offline server.
Yes it works perfectly for the rnaseq pipeline. Downloads all the images.
Maybe it's not that common, but our system is completely offline. I was hoping to transfer the pipeline to it using an external USB drive. We don't have an Internet-based system with singularity at the moment, but we can probably set that up, and install nf-core with conda.
Thanks a lot for reading and considering the issue.
It is pretty common, this is the main use case that we wrote nf-core download for. But I guess most people run nf-core tools natively rather than inside Docker.
I agree that it would be nice to add in Singularity to make this easier, however it strikes me as the kind of thing that could be very difficult to run well.. (But I haven't tried)
Is your feature request related to a problem? Please describe
The docker image doesn't contain singularity. I'd like to use the "download" command to download pipelines with singularity images.
If I try to download a pipeline including images, using the docker image, I get this message:
Describe the solution you'd like
Maybe singularity could be included. But it's a pain to build on Debian/Ubuntu, and would triple the size of the Dockerfile (source code).
Describe alternatives you've considered
I've created an alternative dockerfile to use for this. Edit: It doesn't work. It doesn't write the singularity images.
Additional context
tools-singularity.Dockerfile
(doesn't work)The text was updated successfully, but these errors were encountered: