feat: mount tmp dir in Singularity container #139
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When running
htsinfer.smk
on the login node, an additional--bind
argument has to be specified in the singularity profile, in order to mount the tmp directory that will be used by htsinfer/STAR.Question: Do we want to include that in our singularity profiles in the form of
--bind $TMPDIR
? This solution was tested on the login node, where $TMPDIR points to/scratch
and on Ubuntu 20, where $TMPDIR is empty. On both platforms the rulerun_htsinfer
ran without errors.Disclosure: I don't understand how the issue of a STAR tmp directory is solved inside zarp, and whether that could also be a solution for the
htsinfer.smk
workflow. Input appreciated.Fixes # (issue)