eth-cscs/sarus 1.6.0

on GitHub

Added

• Added the sarus hooks command to list the hooks configured for the engine
• Added the --annotation option to sarus run for setting custom annotations in the OCI bundle. More details here
• Added the --mpi-type option to sarus run for selecting an MPI hook among those configured by the system administrator
• Added a warning message when acquisition of a lock file on the local repository metadata file is taking an unusually long time.
  The message is displayed at a configurable interval (default 10 seconds), until the lock acquisition timeout is reached.
• Added support for the optional defaultMPIType parameter in the sarus.json configuration file. More details here.
• Added support for the optional repositoryMetadataLockTimings parameter in the sarus.json configuration file. More details here.
• Added the AMD GPU OCI hook to provide access to ROCm AMD GPU devices inside the container. More details here
• Added a new OCI hook to perform arbitrary sequences of bind mounts and device mounts into containers.
  The hook is meant to streamline the implementation and usage of advanced features which can be enabled through sets of related mounts.
  More details here.
• Added a note about the Boost minimum required version 1.77 when building on ARM.

Changed

• Sarus will now exit with an error if an operation requiring a lock file on the local repository metadata cannot acquire a lock within the configured timeout duration (default 60 seconds).
  Previously, Sarus would keep attempting to acquire a lock indefinitely.
• When printing error traces, entries related to standard C++ exceptions now provide clearer information
• Updated recommended runc version to 1.1.6
• Updated recommended libnvidia-container version to 1.13.0
• Updated recommended NVIDIA Container Toolkit version to 1.13.0

Fixed

• Fixed a race condition when pulling private images concurrently with the same user
• Fixed a bug which was causing repository metadata files and their corresponding lockfiles to be created or atomically updated with root group ownership after executing a sarus run command.
  The aforementioned files are now correctly created or updated with user and group ownership of the user who launched Sarus.