Hi, I've been trying for a bit to fix `UNIVERSC` m...
# team-maintainers
l
Hi, I've been trying for a bit to fix
UNIVERSC
module. After some debugging I finally manage to make it work on github runner but for that I need to use oras:// protocol for singularity (OOM error during convertion if I use the same container). But doing so, the linting now fails. What would be the best way to deal with this issue ?
m
why oras?
l
Because I need to pull the sif image without the OCI conversion that comes from using directly quay.io url.
m
and the one from galaxy is not working?
l
Unfortunately the tool is using cellranger and isn't available through bioconda.
m
Oh I see
but then if you have a singularity one, it should work with a https link if you have one
l
If I do
Copy code
container "${ workflow.containerEngine in ['singularity', 'apptainer'] && !task.ext.singularity_pull_docker_container ?
        '<https://quay.io/nf-core/universc:1.2.5.1-sif>' :
        '<http://quay.io/nf-core/universc:1.2.5.1|quay.io/nf-core/universc:1.2.5.1>' }"
I get
While checking container encryption: could not open image /path/quay.io-nf-core-universc-1.2.5.1-sif.img: image format not recognized
While the following works
Copy code
container "${ workflow.containerEngine in ['singularity', 'apptainer'] && !task.ext.singularity_pull_docker_container ?
        '<oras://quay.io/nf-core/universc:1.2.5.1-sif>' :
        '<http://quay.io/nf-core/universc:1.2.5.1|quay.io/nf-core/universc:1.2.5.1>' }"
m
Can we host sif on quay.io?
l
I tried and it works 😅
m
but nextflow or singularity seems to have an issue with it
l
Just if you use https:// instead of oras://
singularity run <https://quay.io/nf-core/universc:1.2.5.1-sif>
give
image format not recognized
while
singularity run <oras://quay.io/nf-core/universc:1.2.5.1-sif>
works
p
☝️ this works in any non-ancient apptainer/singularity. There also seems to be 10 or so modules having
oras://
URLS already (for what that is worth).
I say the linter is wrong here.
change my mind
🤣 2