Closed avolkov1 closed 3 years ago
Hi @avolkov1, today only ENROOT_CONFIG_PATH
is passed from the user environment to enroot (through pyxis). The goal was to have pyxis always use the admin defaults for most settings. We want to avoid container import / creation issues caused by users setting those environment variables.
So, the recommendation would be to either use enroot
directly, or ask the cluster admin to modify enroot.conf
. Does that work for you?
Thank you. Yes, that's fine.
Is it possible to override enroot.conf
in the ENROOT_CONFIG_PATH
via customized enroot.conf
(where I would modify ENROOT_DATA_PATH
)? I want to have ~/.config/enroot/enroot.conf
that would take precedence over /etc/enroot/enroot.conf
.
That's not possible, right @3XX0?
Unfortunately no, not right now at least
Ok, thanks.
I want to override the
ENROOT_DATA_PATH
via srun command using pyxis. Currently pyxis seems to ignore environment variableENROOT_DATA_PATH
and only rely on what is set in/etc/enroot/enroot.conf
.Example:
On the node the container is unpacked to:
Instead of:
If using enroot directly without pyxis the
ENROOT_DATA_PATH
is used correctly and the container is unpacked to:But not with pyxis.
Is there a way to have pyxis respect the configuration environment for enroot (enroot configuration)?