SingularityCE 4.4.0 Release

[David Trudgian]

https://github.com/sylabs/singularity/releases/tag/v4.4.0

This is a new minor version, focused around modernisation of code and bugfix improvements as detailed below.

Bug Fixes

• Include the home directory in the --workdir option (which is a modifier of the --contain option). This has always been in the --workdir usage description but the home directory has not actually been included at least since singularity-2.
• Avoid a fatal error when starting fakeroot from suid mode while in an NFS directory.
• Support hosts that have /etc/resolv.conf pointing to a symlink under /run, such as those hosts that are running systemd-resolved. In this case, the symlink is copied into the container and the parent directory of the target of the symlink is bind-mounted from the host. The result is that even if the target of the symlink is replaced with a new file, the container sees the update in /etc/resolv.conf.
• Correctly escape ENV vars when importing OCI containers to native SIF, so that they match podman / docker behaviour.
• Clarify error when trying to build --oci from a non-Dockerfile spec.
• When images are pulled implicitly by actions (run/shell/exec...), and the cache is disabled, correctly clean up the temporary files.
• Ensure singularity-buildkitd runs effective GC at the start of each run.
• Apply --debug flag to buildkit logging correctly.
• Avoid OOM by buffering docker-daemon: images via a temporary file instead of memory. Note that the file is created in $TMPDIR - the dependency involved cannot be instructed to use $SINGULARITY_TMPDIR at this time.

New Features & Functionality

• Add /etc/resolv.conf to the list of host paths that can be prevented from automatic import into the container with the --no-mount option.

Requirements / Packaging

• Requires Go 1.25.6 or above, due to various dependencies.

Thanks / Reporting Bugs

Thanks to our contributors for code, feedback and, testing efforts!

As always, please report any bugs to: https://github.com/sylabs/singularity/issues/new

If you think that you've discovered a security vulnerability please report it to: secu...@sylabs.io

Have fun!