Dave Trudgian

Hmm - I'll try to play around a bit pulling from the CERN repo some more tomorrow. I can pull it without any auth from a first attempt. ``` 04:05...

This needs to be setup so the `-rc` is modified to `~rc` for Debian packaging... (srcver here)... https://github.com/sylabs/singularity/blob/c5dc33d68b10228b583bade8d91add3da9d576ff/debian/rules#L40

Not immediately critical, but should be a blocker for 3.11 RCs closer to November.

Through the work on #872 it's apparent that there's an easy way to do this on an alpine image calling `/bin/busybox sh` in its script hashbang, and then inspecting `/proc/$$/cmdline`...

This is usable from kernel 5.13 - ref -https://www.redhat.com/sysadmin/podman-rootless-overlay We should implement this ASAP as it's basically just relaxing some checks and ensuring the flow is correct through the overlay...

There isn't a direct way to do this. The reconnected FUSE mount is a different mount... and can't be passed into the container again in any simple manner. I believe...

Hi @ast0815, I've dropped the `bug` label here as singularity does not mount anything under `/run/media/xxxx`. That location is usually managed by a Linux Desktop Environment or associated process, which...

Hi @maflister - could you give a bit more background information about what you need to accomplish here? When `singularity` is run without `--fakeroot` you cannot become another user in...

Right - this isn't trivial to do, unfortunately. Because the FUSE binary is running on the host here, but we want the mount to take place in the container, the...

This is still worth pursuing prior to https://github.com/sylabs/singularity/issues/361#issuecomment-940474009 The `--gpus` / `SINGULARITY_GPUS` could override host `NVIDIA_xxx` env vars for this purpose.