Hello, for me pipelines download fails with a seqe...
# tools
n
Hello, for me pipelines download fails with a seqera container and idk why. This test fails with a seqera singularity container. I do not use singularity myself, but GHA tests singularity and seems ok? Edit: I think GHA does not actually test singularity...
I thought that for seqera with singularity, i use
oras://community.wave.seqera.io/container
, I guess that is not the correct way? How do I specify the wave singularity image?
m
I just tested pulling the image that gives the error (because the latest versions of
nf-core pipelines download
should actually support pulling
oras://
) and got this:
Copy code
apptainer pull oras://community.wave.seqera.io/library/quarto_r-plotly_r-quarto_r-tidyjson_pruned:2712f84a83ca0d9a

FATAL:   While pulling image from oci registry: error fetching image to cache: failed to get checksum for oras://community.wave.seqera.io/library/quarto_r-plotly_r-quarto_r-tidyjson_pruned:2712f84a83ca0d9a: ORAS SIF image should have a single layer, found 14
If I use the
docker://
prefix to convert it first, then it works. So the error message was on the point:
Copy code
"oras://community.wave.seqera.io/library/quarto_r-plotly_r-quarto_r-tidyjson_pruned:2712f84a83ca0d9a" is no valid Singularity Image Format  container. To convert from Docker's OCI format, prefix the URI with 'docker://'  instead of 'oras://'.
Bottomline: Singularity/Apptainer use a different container image format. You can’t just prefix a Docker container image with
oras://
, but you need to purpose build it first.
n
Ok, thanks for the explanation, so basically I can either use the image with
docker://
and have singularity deal with it, or build the singularity image on seqera containers?
m
Yes, exactly. If it is available on
depot.galaxyproject
, then you could also pull it via
https://
.
n
Not sure if that is better than using
docker://
, it is certainly more effort to figure out the url
m
If it works to build your required container on Seqera containers, this is preferable over
docker://
, because that conversion is slower. So yes, please use that path in the Singularity image URI.
πŸ‘ 2
s
in my experience the docker -> singularity conversion can also take quite a bit of disk space, which can lead to home directory quotas filling up on a hpc
βœ… 1