Singularity availability on LSF
concatenize opened this issue · 1 comments
concatenize commented
I work on a cluster where I need to do module load singularity
to add singularity to the path. I must do this within every new job, not once at the start -- module load singularity && bsub "singularity"
fails. Based on my experience with a solution similar to what you have here, I suspect that this setup won't allow --use-singularity
. I predict it will fail with the same sort of error, which will manifest like this:
Building DAG of jobs...
WorkflowError:
The singularity command has to be available in order to use singularity integration.
My current workaround is to do load module singularity
as a prefix to the variable you call jobscript
in the wrapper (line 98 of lsf-submit.py).
concatenize commented
Actually, I was totally wrong. I can load singularity once at the start of my session and use it everywhere "downstream".