You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When containerizing an easyconfig that requires an EULA to be accepted (e.g. Intel or NVHPC compilers), the container recipe that easybuild generates does not receive the --accept-eula-for=xxx option that is supplied on the command line.
For example :
results in a recipe that has the following line for easybuild installation of the NVHPC package : eb NVHPC-23.7-CUDA-12.2.0.eb --robot
It feels like the --accept-eula-for command-line option should be injected into the container recipe.
The text was updated successfully, but these errors were encountered:
Hm, one would need to be careful what to include here, as one certainly can't pass all flags, and some things like a --try-amend and such gets a bit confusing at what stage it should appear, before easyconfig is passed to the container or after.
But for --accept-eula-for=XXX makes sense (though I wonder if that should be part of the configuration), and also --cuda-compute-capabilities=xxxx, and probably other things as well.
When containerizing an easyconfig that requires an EULA to be accepted (e.g. Intel or NVHPC compilers), the container recipe that easybuild generates does not receive the --accept-eula-for=xxx option that is supplied on the command line.
For example :
eb NVHPC-23.7-CUDA-12.2.0.eb --accept-eula-for=CUDA -C --container-config bootstrap=yum,osversion=7 --experimental
results in a recipe that has the following line for easybuild installation of the NVHPC package :
eb NVHPC-23.7-CUDA-12.2.0.eb --robot
It feels like the
--accept-eula-for
command-line option should be injected into the container recipe.The text was updated successfully, but these errors were encountered: