[1.2.0] - 2020-06-17

Added

Enabled Sarus to print log messages from the OCI Hooks
Better documentation for ABI Compatibility here
Added User Guide section about running MPI applications without the MPI hook. See here
Added documentation about requiring Linux kernel >= 3.0 and util-linux >= 2.20
Added AddressSanitizer CI job

The glibc Hook is no longer activated by default, unless the --mpi option is used. To activate it explicitly, the new --glibc option of sarus run can be used. See here
Using OCI annotations instead of environment variables to pass information to hooks. It is an internal change, transparent to users, moving towards OCI Hooks independence from Sarus
Most of the Environment Variables for Hooks were renamed. Sarus Administrators should check the new names in the respective hook documentation pages
OCI MPI Hook will now enable MPI "backwards" library injections, issuing a warning. More details here
Improved the retrieval of image manifests from remote registries to better leverage the OCI Distribution specification
Removed the explicit use of the autoclear option when loop-mounting squashfs images. Explicit use of the option causes a failure on
Linux kernels >= 5.4. The autoclear option is still set implicitly by the mount system utility since June 2011 for kernels > 2.6.37.
Updated Spack packages and installation instructions
Updated documentation about the NVIDIA Container Toolkit. See here
The SSH and Slurm global sync hooks now use configurable paths for their resources and are no longer dependant on Sarus-specific directories
Reviewed and updated documentation about runtime security checks. See here
Several improvements to the Continuous Integration workflow

Fixed bug on OCI MPI Hook which failed to run containers having multiple versions of an MPI Dependency library
Runtime security checks no longer fail if a checked path does not exist
Fixed setting of default bind propagation values for custom mounts
Fixed parsing of authentication challenges from the NVIDIA GPU Cloud registry
Fixed the ability to pull images from the Quay.io registry

Compiling now with -fstack-protector-strong as a measure against buffer overflows