-
Notifications
You must be signed in to change notification settings - Fork 215
Add container load scripts for Docker and Podman (#3634 follow up) #3706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add container load scripts for Docker and Podman (#3634 follow up) #3706
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Docs updated in nf-core/website#3463 |
…talled and assume python instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a check if podman/docker cli are installed. Add check if a podman machines or docker daemon is found.
This is a follow up PR on the large
nf-core pipelines downloadrefactor PR #3634, and should be merged AFTER it.This PR replaces the load command for Docker images that is printed to the command line in #3634 with shell scripts copied to the output container folder. I've added support for both Docker and Podman. The latter one might need more testing before releasing it into the wild since we need to manually capture the image name and tag from the
manifest.jsonin the Docker image tar archive, and retag the images. My testing suggests that this approach works however.The load scripts are put inside
nf_core/pipelines/download/load_scripts/and read using theimportlib.resourcesfunction. If there is a better place to keep the files and load them please feel free to change this logic!I've tested the Docker/Podman script on
nf-core/bamtofastqby loading the images into Docker/Podman an dsubsequently running the pipeline with thetestprofile. Since the tests use thetest-datasetrepo I've not run it in a fully offline environment, but instead looked at the pull events from Docker/Podman. From what I can tell it looks to be working correctly. It would however be awesome if someone with experience running pipelines in a fully offline environment tested the scripts.For diff with the base branch see: ErikDanielsson#2
PR checklist
CHANGELOG.mdis updateddocsis updated