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
environment variables in env.json that expand environment variables are treated as literals, and not expanded. Not exactly a bug, but it has an impact on e.g. the julia uenv: "JULIA_DEPOT_PATH": "$SCRATCH/${HOSTNAME%%-*}/juliaup/depot"
print an error message that gives CSCS staff a hint on how to configure their token on a failed pull, copy or rm call
The text was updated successfully, but these errors were encountered:
A list of rough edges to clean up:
uenv start ./lammps.squashfs
requires an absolute path... relax to a relative path starting with./
or../
. allow relative paths for squashfs images #53uenv image pull --token=X --username=Y
gives an awful error message when there is an error in either username or token. oras messages for invalid username and token #55uenv image add
doesn't work when the image being added is a squashfs file inside the repository.image copy
andimage delete
confuse users, because they clash withimage add
andimage rm
uenv start/run
give a cryptic error message when a uenv is already loaded/ user-friendly error message when run/start in a session #54env.json
that expand environment variables are treated as literals, and not expanded. Not exactly a bug, but it has an impact on e.g. thejulia
uenv:"JULIA_DEPOT_PATH": "$SCRATCH/${HOSTNAME%%-*}/juliaup/depot"
pull
,copy
orrm
callThe text was updated successfully, but these errors were encountered: