BENCH-9858: Declare a container for each Nextflow process - #26
Open
samhornstein wants to merge 2 commits into
Open
samhornstein wants to merge 2 commits into
samhornstein wants to merge 2 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The tutorial assigned one image through its execution profiles, so it did not show how Nextflow modules declare their own software. Each greeting process now declares
debian:12-slim; Docker and Google Batch use those declarations while the standard profile continues to run local commands.The guide explains per-process selection and image inspection. Existing
NF_CONTAINERoverrides should move to a module declaration or awithNameselector.Validation
nextflow inspectresolved all three process images for Docker and Workbench (using dummy cloud context; no Batch jobs submitted).Jira: BENCH-9858