R. P. Taylor

Hi, No there is no user info embedded in the /etc/passwd or /etc/group files in the container image. Usually it will be only the minimal set of system accounts defined...

Hi Greg, Yes that is correct. > If that is the case, I think the easiest path forward would be to add those pieces to the appropriate files where you...

Part 1: possible changes in Singularity Currently the warnings/failures occur here: https://github.com/hpcng/singularity/blob/master/pkg/syfs/syfs.go#L48 This code is slightly over-ambitious in the sense that it does a full lookup of user info -...

Side note: perhaps I am mistaken but this appears to be checking user's capability based on their GECOS display name (which could include spaces and other special characters etc) as...

Part 2: it would be nice to find a solution in Go without having to change Singularity code. In particular if I could just `export USER=whatever` , but in my...

Similar to #5598 and #5757

Yes, still relevant.

Still interested in a way to do this.

https://github.com/theskumar/python-dotenv/pull/245 this added a warning output if verbose is true, which can help with visibility but doesn't address the issue if you want a strict requirement on config file existence.

Related to https://github.com/restic/restic/issues/2202 I think supporting immutable backups is a good idea, I was just trying to figure out how to do it myself. S3 (incl Backblaze S3) supports immutable...