Add readOnlyInputs option for CharliecloudBuilder #3590
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.
This merge request is to add the
readOnlyInputs
option as discussed in the Charliecloud and shared cacheDir #3367 issue and following the Add readOnlyInputs option for CharliecloudBuilder #3477 merge requestWith this modification:
readOnlyInputs
value isfalse
readOnlyInputs
istrue
;-w
option is removed from the commandFor example, if I try to bind
/home/user/workdir/
to/home/
the bound path will be/home
to/home
. By doing that, charliecloud doesn't try tomkdir -p /home/user/workdir/
within the read-only container, the external path is bound at the/home
directory level so all the subfolders are accessible with the user rights. If one tries to bind/
I added an expection.Signed-off-by: Laurent Modolo [email protected]