2 remove runcript from singularity build - #4
Conversation
pditommaso
left a comment
There was a problem hiding this comment.
leave to @marcodelapierre to confirm
|
Working in my tests, leave Marco propose any change post-merging |
There was a problem hiding this comment.
Changes look good, two important comments, especially the first one:
-
If still as is, I strongly recommend using
singularity execinstead ofsingularity run, as this is the correct, supported usage for Singularity (see singularity docs, https://docs.sylabs.io/guides/latest/user-guide/quick_start.html#executing-commands vs https://docs.sylabs.io/guides/latest/user-guide/quick_start.html#running-a-container -
The image hash for singularity vs docker is different, right?
yes
The rationale was to align to the Docker entrypoint behaviour, especially for the problem of Conda initialization. See here. However, I understand that also |
|
Hi @pditommaso have a look at this comment of mine: seqeralabs/wave#288 (comment). Although I need to have a closer look at the scripts/requirements for mamba-org/micromamba-docker#155 (comment), I am pretty sure that the It looks to me like right now Nextflow is still using So please let me know how you would best like to follow up on this, based on the extra info above. |
|
There has been a tentative to use However I've reverted this change in the last release nextflow-io/nextflow@c1cc60dd |
|
Thanks for sharing these code refs Paolo 👍 |
This PR will remove %runscript from singularity image and make it simple