nextflow-io / nextflow-io/nextflow
Support for bulker multainer
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
New feature
Multainer support will really enhance the utility of Nextflow by potentially decreasing the number of processes in any given workflow. May even improve efficiency as more work will get done on any given compute instant and wait time between computes will be low.
Use case
Often times we need multiple tools within a given process. So we have to split the process into different cascading processes where each process uses a different tool-specific docker. To avoid this we could support multainer like bulker
Suggested implementation
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
The issue names no files, tests, or entry points. Start by locating Nextflow’s container and process-execution handling, then determine the design needed for bulker-style multi-container support. Done means a process can use multiple tools through the supported container setup, with tests documenting the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100