apptainer-1.3.0 available in EPEL, Fedora, and Ubuntu PPA; answers to 1.3.0 questions

['Dave Dykstra' via announce]

apptainer-1.3.0 is now in the epel and Fedora updates repositories. It's also in the Ubuntu PPA.

Also, there were questions raised about CVEs mentioned in the epel & Fedora updates. They were only moderate severity denial of service vulnerabilities in a deeply buried go library dependency so they weren't included in an announcement before. There are now details in the github release announcement in case anyone is interested.

There have also been questions about how to prevent the use of FUSE outside of Apptainer-1.3.0 in SUID mode, for system administrators who want to do that. That can be done by removing the "fuse" package so that the privileged "fusermount" program is not on a system. Apptainer does not use it, but SUID mode does now require the fuse kernel module to be available. That is available by default on all major Linux OSes but some system administrators have removed it.

Dave

On Thu, Mar 14, 2024 at 09:08:08AM -0500, Dave Dykstra wrote:
> apptainer-1.3.0 is now available in the epel-testing yum repository and in the Fedora 39 & 40 updates-testing repository. Please test it if you can; if no significant problems are found it should be promoted to the stable repositories in about a week. It can also be installed with "tools/install-unprivileged.sh -v 1.3.0". For installation details see
> https://apptainer.org/docs/admin/latest/installation.html
>
> The documentation at the "latest" links should now match the 1.3.0 behavior. If you find any anomalies in the documentation please create an issue in the corresponding github repository.
>
> Dave
>
> On Tue, Mar 12, 2024 at 08:56:43PM -0700, Krishna Muriki wrote:
> > Apptainer v1.3.0 is now available.
> >
> > https://github.com/apptainer/apptainer/releases/tag/v1.3.0
> >
> > Glad to announce the release of Apptainer v1.3.0. This is the next major release with a lot of new features, functionality, bug fixes and changes. Please read the release notes, build and test it in your environment and report problems to
> > https://github.com/apptainer/apptainer/issues
> >
> > Questions can be raised here or on the Apptainer #general slack channel.
> >
> > Apptainer v1.3.0 Release Notes
> > Changed defaults / behaviours
> >
> > * FUSE mounts are now supported in setuid mode, enabling full functionality even when kernel filesystem mounts are insecure due to unprivileged users having write access to raw filesystems in containers.
> >
> > When allow setuid-mount extfs = no (the default) in apptainer.conf, then the fuse2fs image driver will be used to mount ext3 images in setuid mode instead of the kernel driver (ext3 images are primarily used for the --overlay feature), restoring functionality that was removed by default in Apptainer 1.1.8 because of the security risk.
> >
> > The allow setuid-mount squashfs configuration option in apptainer.conf now has a new default called iflimited which allows kernel squashfs mounts only if there is at least one limit container option set or if Execution Control Lists are activated in ecl.toml. If kernel squashfs mounts are are not allowed, then the squashfuse image driver will be used instead.
> > iflimited is the default because if one of those limits are used the system administrator ensures that unprivileged users do not have write access to the containers, but on the other hand using FUSE would enable a user to theoretically bypass the limits via ptrace() because the FUSE process runs as that user.
> >
> > The fuse-overlayfs image driver will also now be tried in setuid mode if the kernel overlayfs driver does not work (for example if one of the layers is a FUSE filesystem).
> >
> > In addition,
> > if allow setuid-mount encrypted = no then the unprivileged gocryptfs format will be used for encrypting SIF files instead of the kernel device-mapper. If a SIF file was encrypted using the gocryptfs format, it can now be mounted in setuid mode in addition to non-setuid mode.
> >
> > * The four dependent FUSE programs for various reasons all now need to be compiled from source and included in Apptainer installations and packages.
> > Scripts are provided to make this easy; see the updated instructions in INSTALL.md<https://github.com/apptainer/apptainer/blob/v1.3.0/INSTALL.md >. The bundled squashfuse_ll is updated to version 0.5.1.
> >
> > * Change the default in user namespace mode to use either kernel overlayfs or fuse-overlayfs instead of the underlay feature for the purpose of adding bind mount points. That was already the default in setuid mode; this change makes it consistent. The underlay feature can still be used with the --underlay option, but it is deprecated because the implementation is complicated and measurements have shown that the performance of underlay is similar to overlayfs and fuse-overlayfs.
> > For now the underlay feature can be made the default again with a new preferred value on the enable underlay configuration option.
> > Also the --underlay option can be used in setuid mode or as the root user, although it was ignored previously.
> >
> > * Prefer again to use kernel overlayfs over fuse-overlayfs when a lower layer is FUSE and there's no writable upper layer, undoing the change from 1.2.0. Another workaround was found for the problem that change addressed. This applies in both setuid mode and in user namespace mode (except the latter not on CentOS7 where it isn't supported).
> >
> > * --cwd is now the preferred form of the flag for setting the container's working directory, though --pwd is still supported for compatibility.
> >
> > * When building RPM, we will now use /var/lib/apptainer (rather than /var/apptainer) to store local state files.
> >
> > * The way --home is handled when running as root (e.g. sudo apptainer) or with --fakeroot has changed. Previously, we were only modifying the HOME environment variable in these cases, while leaving the container's /etc/passwd file unchanged (with its homedir field pointing to /root, regardless of the value passed to --home). With this change, both value of HOME and the contents of /etc/passwd in the container will reflect the value passed to --home if the container is readonly. If the container is writable, the /etc/passwd file is left alone because it can interfere with commands that want to modify it.
> >
> > * The --vm and related flags to start apptainer inside a VM have been removed. This functionality was related to the retired Singularity Desktop / SyOS projects.
> >
> > * The keyserver-related commands that were under remote have been moved to their own, dedicated keyserver command. Run apptainer help keyserver for more information.
> >
> > * The commands related to OCI/Docker registries that were under remote have been moved to their own, dedicated registry command. Run apptainer help registry for more information.
> >
> > * The the remote list subcommand now outputs only remote endpoints (with keyservers and OCI/Docker registries having been moved to separate commands), and the output has been streamlined.
> >
> > * Adding a new remote endpoint using the apptainer remote add command will now set the new endpoint as default. This behavior can be suppressed by supplying the --no-default (or -n) flag to remote add.
> >
> > * Skip parsing build definition file template variables after comments beginning with a hash symbol.
> >
> > * Improved the clarity of apptainer key list output.
> >
> > * The global /tmp directory is no longer used for gocryptfs mountpoints.
> >
> > * Updated minimum go version to 1.20
> >
> > New Features & Functionality
> >
> > * The remote status command will now print the username, realname, and email of the logged-in user, if available.
> > * Add monitoring feature support, which requires the usage of an additional tool named apptheus, this tool will put apptainer starter into a newly created cgroup and collect system metrics.
> > * A new --no-pid flag for apptainer run/shell/exec disables the PID namespace inferred by --containall and --compat.
> > * Added --config option tokeyserver commands.
> > * Honor an optional remoteName argument to the keyserver list command.
> > * Added the APPTAINER_ENCRYPTION_PEM_DATA env var to allow for encrypting and running encrypted containers without a PEM file.
> > * Adding --sharens mode for apptainer exec/run/shell, which enables to run multiple apptainer instances created by the same parent using the same image in the same user namespace.
> >
> > Developer / API
> >
> > * Changes in pkg/build/types.Definition struct. New .FullRaw field introduced, which always contains the raw data for the entire definition file. Behavior of .Raw field has changed: for multi-stage builds parsed with pkg/build/types/parser.All(), .Raw contains the raw content of a single build stage. Otherwise, it is equal to .FullRaw.
> >
> > Bug fixes
> >
> > * Don't bind /var/tmp on top of /tmp in the container, where /var/tmp resolves to same location as /tmp.
> > * Support parentheses in test / [ commands in container startup scripts, via dependency update of mvdan.cc/sh<http://mvdan.cc/sh >.
> > * Fix regression introduced in v1.2.0 that led to an empty user's shell field in the /etc/passwd file.
> > * Prevent container builds from failing when $HOME points to a non-readable directory.
> > * Fix the use of nvidia-container-cli on Ubuntu 22.04 where an ldconfig wrapper script gets in the way. Instead, we use ldconfig.real directly.
> > * Run image drivers with CAP_DAC_OVERRIDE in user namespace mode. This fixes --nvccli with NVIDIA_DRIVER_CAPABILITIES=graphics, which previously failed when using fuse-overlayfs.
> >
> > Release change
> >
> > * Releases will generate apptainer Docker images for the Linux amd64 and arm64 architectures.
> >
> > --
> > You received this message because you are subscribed to the Google Groups "announce" group.
> > To unsubscribe from this group and stop receiving emails from it, send an email to announce+u...@apptainer.org<mailto:announce+u...@apptainer.org>.