Pass user env/flag binds into container as SINGULARITY_BIND #5670
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 of the Pull Request (PR):
In prior versions of singularity the
SINGULARITY_BIND
env var wouldpass into the container. I've seen
SINGULARITY_BIND
examined incontainers to e.g. check that a user specifically bound in a data
directory where that's necessary.
Restore so that
SINGULARITY_BIND
in the container reflects userdefined env var, and also now flag binds.
Checking
SINGULARITY_BIND
in a container like this is admittedly fragile - but this PR is concerned with allowing it, as it has been requested in #5599This fixes or addresses the following GitHub issues:
Before submitting a PR, make sure you have done the following:
make testall
Attn: @singularity-maintainers