Draft
Conversation
Contributor
Author
|
Although we don't have the symlinks yet, I can actually already test this in the container - it will just create the symlinks in What I did: Works as intended. After implementing the variant symlinks, we should retest, try to use the |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We'll need the following variant symlinks to be in place before this script can work as intended:
And then:
This can then be quite easily tested from within the container:
This should error out stating that the variant symlink resolves to
/dev/null. Then, you can change/etc/cvmfs/default.localto set e.g.EESSI_NVIDIA_OVERRIDE_DEFAULT(e.g. to/opt/eessi/nvidia) and run the linking script again - this should the install the symlinks.