nextflow-io / nextflow-io/nextflow
`nextflow inspect` does not reflect `singularity.registry`
Open
Nobody has claimed this yet.
bug
software/singularity
triage/investigate
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Bug report
The nextflow inspect command does not properly account for the singularity.registry setting when reporting containers.
Expected behavior and actual behavior
I have a process:
process EXAMPLE {
container google/deepvariant:1.8.0
...
}
I have the following config:
docker.registry = 'docker.io'
singularity.registry = 'docker.io'
Running inspect with docker profile:
{
"name": "DEEPVARIANT_RUNDEEPVARIANT",
"container": "docker.io/google/deepvariant:1.8.0"
},
Running with singularity profile:
{
"name": "DEEPVARIANT_RUNDEEPVARIANT",
"container": "google/deepvariant:1.8.0"
},
Environment
- Nextflow version: 25.04.3
- Java version: openjdk version "21.0.7" 2025-04-15 LTS
- Operating system: macOS
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 with the nextflow inspect command and compare its container reporting under the docker and singularity profiles using the configuration shown. Trace how each registry setting is applied, then verify that the singularity output includes the configured registry while preserving the existing docker output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, groovy
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100