-
Notifications
You must be signed in to change notification settings - Fork 39
Adding non-standard ways to use EESSI #387
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: main
Are you sure you want to change the base?
Conversation
|
True, in my Ubuntu works but seems that its because I have CVMFS already available, I tested it in other systems without CVMFS and the same error message shows :( |
clarirfication for cvmfsexec
orted_wrapper_dir=$(dirname $0) | ||
export PATH=$(echo $PATH | tr ':' '\n' | grep -v $orted_wrapper_dir | tr '\n' ':') | ||
|
||
~/bin/cvmfsexec_eessi.sh orted "$@" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this work? I imagine that you need to load the modules you need in your cvmfsexec_eessi.sh
script or it will not find orted
inside the container
docs/getting_access/non_standard.md
Outdated
|
||
## Via `squashfs` + cvmfs's `shrinkwrap` utility | ||
|
||
CernVM-FS provides the Shrinkwrap utility, allowing users to create a portable snapshot of a CVMFS repository. This can be exported and distributed without the need of a CVMFS client or network access. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should link to the CVMFS docs on this early on.
Co-authored-by: ocaisa <alan.ocais@cecam.org>
Co-authored-by: ocaisa <alan.ocais@cecam.org>
Co-authored-by: ocaisa <alan.ocais@cecam.org>
Co-authored-by: ocaisa <alan.ocais@cecam.org>
cvmfs-2.13.0 was released a few minutes ago, so the approach with shrinkwrap should work out-of-the-box if you have that version available. This also means I can start working on a script to manage this once our client containers are updated |
As per this issue: https://gitlab.com/eessi/support/-/issues/119
First batch regarding the cvmfsexec usage. A couple of thoughts:
Not sure why it mentions rpm if its a deb system, specially if in my ubuntu worked. Tbh I think their environment was polluted by some local testing they were doing and we will try again later, but I paste it here just to have it in mind in case we see it again.