Split the single pipeline container which all processes use into containers used only in a given processes
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Nextflow
- Stars
- 9
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Description of feature
All processes currently use a single container which was created using the Dockerfile found under assets/Docker. Optionally, we would have one container for a given process rather than one container for all processes in the pipeline.
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 by inspecting the Dockerfile under assets/Docker and tracing how it is used by the pipeline's processes. Define the per-process container boundaries and verify that each process uses only its intended container while preserving the existing pipeline behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100