Singularity images naming convention and writing permission to cache library #5110
Unanswered
LouisLeNezet
asked this question in
Q&A
Replies: 2 comments 3 replies
-
I think this is already supported by using env variables |
Beta Was this translation helpful? Give feedback.
3 replies
-
Just to add a precision: the shared directory mentioned by @LouisLeNezet is the CVMFS mountpoint corresponding to https://depot.galaxyproject.org/singularity/ It can only be mounted at |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I'm running nextflow on an HPC and numerours singularity image are already available in a shared directory.
We do not have write access to it but it would be nice to use all the image already present.
The issue I'm facing is that the images are written as follow as
multiqc-1.21--pyhdfd78af_0.img
and nextflow is looking fordepot.galaxyproject.org-singularity-multiqc-1.21--pyhdfd78af_0.img
.I guess that the issue originate from this code.
Would it be possible to configure this in the config file ?
Also, as we do not have writing access to the singularity directory nextflow might crash if the image is not present.
Here I remove the write access to
singularity2
folder.java.io.FileNotFoundException: work/singularity2/.depot.galaxyproject.org-singularity-samtools-1.19.2--h50ea8bc_0.img.lock (Permission denied)
In this case it would be nice to have a recovery mechanism, like using the default
work/singularity
in case the image is not present in the library ?Thanks !
Beta Was this translation helpful? Give feedback.
All reactions