[META-ISSUE] Migrate modules to Seqera Containers
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
Seqera Containers is a new service to provide Docker + Singularity containers from any Conda / PyPI packages. Images are generated on demand and can include multiple packages.
Links for background:
- https://seqera.io/containers/
- https://seqera.io/blog/introducing-seqera-pipelines-containers/
- https://day1hpc.com/post/announcing-seqera-containers-supported-by-aws/
- Recent bytesize talk with YouTube recording
We should strip out the BioContainers quay.io docker images + Galaxy server Singularity images and replace with image URIs from Seqera Containers.
We should use this change as an opportunity to rethink the optimal code structure for defining image names. This is currently under discussion. Group consensus can be posted here once achieved for broader community approval.
Milestone to track broad progress on this update: https://github.com/nf-core/modules/milestone/6
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
Read the linked Seqera Containers background material and review the existing module image definitions tracked in milestone 6. Wait for the code-structure discussion to reach consensus before starting. Done means the BioContainers quay.io images and Galaxy server Singularity images are replaced with Seqera Containers image URIs across the tracked modules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100