Allow extra volume bindings and custom wrapper config file #678
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.
This PR:
a) Adds a new
ODK_BINDS
variable to therun.sh
wrapper script, which can be used to specify extra volume bindings within the Docker or Singularity container. Use as follows:b) Adds a new
ODK_DOCKER_OPTIONS
variable, to allow user to pass any custom options to the invocation ofdocker run
. Another variable,ODK_SINGULARITY_OPTIONS
, does the same for the invocation ofsingularity exec
.c) Allows to set variables for the
run.sh
wrapper in a file namedrun.sh.conf
(in the same directory as the wrapper script itself). That file should contain standard Bourne-shell variable declarations, and will be sourced (if it exists) by the wrapper script. It allows to use variables such as the newODK_BINDS
,ODK_DOCKER_OPTIONS
, but also the pre-existingODK_IMAGE
orODK_TAG
, once and for all in therun.sh.conf
file, instead of having to export them to the user’s environment or set them every time the wrapper script is invoked.closes #675