nextflow-io / nextflow-io/nextflow
Basic architecture awareness when using singularity/apptainer - container image name
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
This is a companion feature request to #7616.
If we would gain the ability to get the correct architecture image for multi-architecture sources, it would be nice to know that we don't run into collisions.
Therefore, it would be nice that if we have a process.arch specified (possibly fitting a whitelist that cause it to be forwarded to the pull command as per #7616), it's desirable that (some form of) the architecture is included in the cached image name.
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 reading companion issue #7616 and tracing the Singularity/Apptainer pull command and cached image-name handling. Follow how a specified process.arch could be validated and forwarded, then define how the architecture is included in cached names so supported multi-architecture images do not collide.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100