DrDaveD

What do you think of apptainer/apptainer-userdocs#127 as a solution?

I wanted to try to investigate what was different about the two environments, but I can't reproduce the case of succeeding with suid and failing without. The testing I was...

> @DrDaveD did you get a chance to take a look at the outputs to figure out why the `/proc/[PID]/fd/[fd]` are not accessible across processes in no-suid mode? I did,...

You're asking if there's an apptainer-compose? No, but the existing [singularity-compose](https://singularityhub.github.io/singularity-compose/) should work the same, I assume. I haven't tried it.

That sounds like pre-apptainer 1.1.0 behavior. Can you run `apptainer --version` on your cluster to see if it is running the correct version?

Do you have `squashfuse_ll` or `squashfuse` available on the cluster? If you don't it should have shown with additional `INFO` messages.

Hmm, on my system if `squashfuse` and `squashfuse_ll` are missing I see ``` INFO: squashfuse not found, will not be able to mount SIF FATAL: container creation failed: mount /proc/self/fd/3->/var/apptainer/mnt/session/rootfs...

Oh, and if `fuse2fs` is also missing I get ``` INFO: squashfuse not found, will not be able to mount SIF INFO: fuse2fs not found, will not be able to...

So I'm not sure what's going on in your case. Clearly `squashfuse` or most preferably the multithreaded `squashfuse_ll` need to be available on the cluster, but I would still like...

The only other option is compiling `--with-suid` (or installing the `apptainer-suid` package if you're using pre-built packages). Could you please post that debugging output?