DrDaveD
DrDaveD
Does it sometimes change the symlink, or does it only recreate the destination of the symlink? I don't think there's any way we'd be able to detect a change in...
Oh, and worse, even if we made it a symlink we would have to bind-mount the destination of the symlink and it would have the same problem. So thanks for...
Oh I guess that it might be able to bind the *directory* that the destination of the symlink is in and in that way see updates to the file. But...
Extending the `--no-mount` option to also work with /etc/resolv.conf sounds like a very straightforward solution. In fact it's almost a bug that that isn't already implemented (at least it didn't...
We should do the `--no-mount` option, but at the community meeting today there was also agreement that automatically detecting a symlink at /etc/resolv.conf and binding in the directory it points...
> But that requires mounting a fuse filesystem, which might not be doable. Apptainer already does a lot with fuse filesystems so I would think it would be "doable". However...
I had independently figured out part of the solution and then found it was fully written up at https://github.com/apptainer/singularity/issues/5075#issuecomment-972934341. SINGULARITY_SHELL is still what's needed, not APPTAINER_SHELL. The problem is that...
The documentation at https://geniac.readthedocs.io/en/latest/conda.html#singularity might be helpful, although it says setting SINGULARITY_SHELL is not recommended and I don't understand why.
Oh, that's a good point. Normally I think running the user's bashrc is a good thing, but a host conda environment could clash with the one in the container. My...
I have now added some documentation about this. See the note at the end of the [`%environment`](https://apptainer.org/docs/user/latest/definition_files.html#environment) section.