Skip to content
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

Replace vanilla Linux Biocontainer with Ubuntu #1557

Merged
merged 1 commit into from
Apr 22, 2022

Conversation

drpatelh
Copy link
Member

@matthdsm
Copy link
Contributor

Is there an option to use a base alpine container for these utilities? That would limit the network traffic needed to pull the images?

@drpatelh
Copy link
Member Author

We could do but like with all other modules it makes sense to use a container that has both Docker and Singularity images that we can pull directly, and this particular container does.

@edmundmiller
Copy link
Contributor

Is there an option to use a base alpine container for these utilities? That would limit the network traffic needed to pull the images?

You could override the container with your nextflow.config. I'd vote we let anyone who cares about that set it in their institutions' config.

Also, 22.04 got released yesterday https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668 just in case you weren't aware that was an option.

@drpatelh
Copy link
Member Author

22.04 doesn't have a Singularity container 😏 But no reason we can't update in the future. At this point, I think we just need access to basic Linux utilities so I think it's fine. As you mentioned, you can always override the configuration with your own container definitions.

@drpatelh drpatelh merged commit 9aadd9a into nf-core:master Apr 22, 2022
@@ -2,10 +2,10 @@ process UNTAR {
tag "$archive"
label 'process_low'

conda (params.enable_conda ? "conda-forge::tar=1.34" : null)
conda (params.enable_conda ? "conda-forge::sed=4.7" : null)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the only change that I don't get. Isn't it much more explicit to install tar in the untar module rather than sed which happens to include tar?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good spot! Missed that in the copy/paste. Wondering whether we need to care about this specifically because these tools should all be installed in the base Conda env anyway right? So do we go for standardisation here where we always define sed for modules using the ubuntu image or do we define the specific tools we are using? The latter could also be a pain in general because in most instances you will want to use multiple utilities like cat, awk, sed in the same module etc

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair point. If there's a way to pull in multiple standard tools that are also available in the container images, then that's probably preferable. Would that make available ps btw? I think that's needed for resource tracing, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants