Set up read-only container image store on NFS #13
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 sets up read-only container image store on NFS. User can modify the list of images in src/containerimages.conf prior running
setup.sh
. The actual images are pulled when starting the slurm controller.Other solutions that I have been thinking of: 1. creating the read-only disk or just a tar file separately and pass as a hidden input to wolf task, and add corresponding change in wolf script. 2. creating the read-only disk and burning the logic of mounting disk into slurm worker startup script. However it seems to me that the latter two approaches are more involved.