DrDaveD
DrDaveD
If it's a race condition, then presumably trying something many times that runs a short time should eventually trigger it. Can you help us by identifying an MPI job that...
But as you pointed out in #2754, the docs do list an exception: "unless its path contains symlinks resolving to different locations on the host vs inside the container." So...
So you're guessing that your system admins have turned it off? I don't see that as a configuration option, unless it's the option that turns off all user bind mount...
How about binding a file into the`/.singularity.d/env` directory? Those all get executed at startup.
That's fine. They could each bind in their own file when they run the container.
Oh, I expect those are being interpreted by the mvdan.cc/sh interpreter and put into the environment. How about instead setting APPTAINERENV_BASH_ENV, assuming $SHELL is bash? That only appears to work...
According to the [documentation](https://apptainer.org/docs/admin/1.3/installation.html#nfs), "when building a container your TMPDIR / APPTAINER_TMPDIR should not be set to an NFS location." So try setting that to /tmp or some other local...
I don't have a nix host to run this on. When I tried it on rocky8 I got `Bus error (core dumped)`. Can you make a reproducer for a RHEL...
@Swindle98 that's a different issue. When building from source you need to follow the [AppArmor instructions in INSTALL.md](https://github.com/apptainer/apptainer/blob/main/INSTALL.md#apparmor-profile-ubuntu-2310).