sarus
sarus copied to clipboard
OCI-compatible engine to deploy Linux containers on HPC environments.
I would like to be able to have control as a user over Sarus by setting some environment variables. In principle, one could take control of the entire config options...
``` $ sarus pull stabbles/sarus-breaks [153440.815513349] [nid003192-256744] [main] [ERROR] Error trace (most nested error last): #0 parseJSON at "Utility.cpp":1027 Error parsing JSON string: '{ "mediaType":"application/vnd.oci.image.layer.v1.tar+gzip", "digest":"sha256:342a65410489fb8ec0e87f1f9af0b7da91ba922f689345b0007380e19cc2703f", "size":18007253 } ], "annotations":{...
``` #0 checkThatPathIsRootOwned at "SecurityChecks.cpp":78 Path "/home/harmen/spack/opt/spack/linux-ubuntu22.10-zen2/gcc-12.2.0/squashfs-4.5.1-kyy4hxwwoqqwhrws35zhcgcqcmn56yah/bin/mksquashfs" must be owned by root in order to prevent other users from tampering its contents. Found uid=1000, gid=1000. ``` Why?
Hi @madeeks, is there any specific reason why the Spack recipe is sitting in this repo rather than in the main Spack repo? If there is any technical blocker, I...
Sarus file-lock acquisition times out for files in ~/.sarus when user homes are shared via NFS4.X (but works with NFS3): `[1229.860589957] [node01-6321] [Flock] [WARN] Still attempting to acquire lock on...