https://nf-co.re logo
Join Slack
Powered by
Hey folks I'm trying to figure out something about...
# variantbenchmarking
n
Hey folks I'm trying to figure out something about what the interplay between the 
docker.registry
parameter is and the custom images in the repo. The registry is set here: https://github.com/nf-core/variantbenchmarking/blob/1.2.0/nextflow.config#L228 And running in docker only mode the bcftools/reheader module pulls from 
biocontainers/bcftools:1.20--h8b25389_0
which maps to: quay.io/biocontainers/bcftools:1.20--h8b25389_0 however with custom/bedtools_intersect we're pulling from 
<http://community.wave.seqera.io/library/pybedtools_pandas:6eae56b7891a94c6|community.wave.seqera.io/library/pybedtools_pandas:6eae56b7891a94c6>
which is a full URL to a wave registry. Is there some internal logic I'm not aware of that's overriding the docker registry set in the first link I set above when community.wave is pre-pended in the container name?
✅ 1
m
So I have a good explanation for you
Nextflow is way too smart for our own good
If you specify a full URI, nextflow will use that
if the URL is not full, nextflow will use the registry which by default is docker.io
It's similar to the way one can run 
nextflow run hello
what nextflow actually does is it knows that the default hosting for scripts is github, and the default org is nextflow.io
So you do 
nextflow run hello
, but it's actually 
nextflow run <https://github.com/nextflow-io/hello>
but if you specify any other pipeline you need to add another org on top, or even another hosting than github
n
Ah, that does make sense. Thank you, that clears it up for me!
🙏 1
Open in Slack
PreviousNext
Powered by