Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting $SINGULARITY_TMPDIR environment variable #203

Open
miller-alexander opened this issue Dec 11, 2023 · 0 comments
Open

Setting $SINGULARITY_TMPDIR environment variable #203

miller-alexander opened this issue Dec 11, 2023 · 0 comments

Comments

@miller-alexander
Copy link

Our team uses Caper/WDL on a SLURM backend with Singularity. We've been encountering a "container collision" issue i.e. when Singularity unpacks the image, there is a chance that it unpacks the image for two or more parallel tasks to the same location. If we can set the $SINGULARITY_TMPDIR environment variable, we should be able to ensure that Singularity always unpacks the image in a location unique to the job (rather than unique to the task name).

Right now, we can set Caper to run in dry-mode, edit the backend configuration to include setting the $SINGULARITY_TMPDIR, then run Caper on the custom backend, but it would be much simpler to be able to pass the $SINGULARITY_TMPDIR value to Caper itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant