[WIP] Add functionality for updating an existing compatibility layer #229
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixes EESSI#226 Since this is pretty relevant to security, I am inclined to point these variable symlinks to `/dev/null` by default but that does not actually address the problem being discussed in EESSI#226 (having to harass the admins to link the CUDA drivers). If we can have logic in our CVMFS configuration then maybe we can address that.
|
Tried it with a bind mount from the host, but that doesn't work, as the files are then owned by the cvmfs user. This leads to all sorts of permission errors in the Prefix environment, e.g. |
bedroge
force-pushed
the
update_compat_layer
branch
from
d9288eb to
3d15aa0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Attempt to make it possible to rerun the playbook on top of an existing compat layer. Will require some changes in the installation script, as it now bind mounts an empty host dir as
/cvmfs/software.eessi.io, instead it should probably just fusemount the CVMFS repo inside the container.