Always use fuse mounts by default in EESSI container, only use bind mounts when explicitly requested#57
Conversation
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-jsc architecture:aarch64/nvidia/grace |
|
New job on instance
edit: this failed because of issues with the EB configuration, not caused by this PR. |
9e60de2 to
51d3d91
Compare
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-jsc architecture:aarch64/nvidia/grace |
|
New job on instance
|
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-jsc architecture:aarch64/nvidia/grace |
|
New job on instance
|
|
I've made some additional changes in 6610e7e, as I just found other parts in the scripts where we loop over the repositories and where it only checked for |
|
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-jsc architecture:aarch64/nvidia/grace |
|
New job on instance
|
casparvl
left a comment
There was a problem hiding this comment.
I think we should also investigate if we can somehow do bind-mounting on hosts that have the repo mounted and have a non-standard host-injections, this solves some immediate build issues. Looks good to me, test by Bob was succesful.
I've removed the cowsay test easystack, hope that's ok with you @bedroge , but then it can be merged right away :)
Solves #56 by reverting the change which made bind mounts the default on systems where
/cvmfs/software.eessi.iomounted on the host. This could cause issues with the host injections folder, if this system uses a non-standard path (something else than/opt/eessi).Bind mounts can still be used, but have to be explicitly enabled by using something like:
./eessi_container.sh -r myrepo,mount=bindAlso improves the parsing of some variables, which could have a trailing newline in case they are the last/only argument. It's removing them using
${myvar%$'\n'}(see https://unix.stackexchange.com/a/57128).