nextflow-io / nextflow-io/nextflow
`nextflow launch` support launchContainer field
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
New feature
The Seqera API supports the launchContainer field, but this is not exposed in the nextflow launch CLI. It's important to be able to control the Nextflow version so it matches your local version.
Use case
If my remote Nextflow uses 25.04 by default but my local version uses 25.10, I may wish to select the launchContainer as myregistry.io/nextflow:25.10.4
Suggested implementation
nextflow launch -launch-container myregistry.io/nextflow:25.10.4
Default is null and ignored in the POST request.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the nextflow launch CLI entry point and trace how its options are mapped into the Seqera API POST request. Add support for the -launch-container value while leaving the field null and omitted by default, then verify that a specified container is sent correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100