OCI-compatible engine to deploy Linux containers on HPC environments.
com.hooks.ssh.port OCI annotation, which allows to customize the port used by the Dropbear server.--verbose or --debug global command-line options).SERVER_PORT_DEFAULT environment variable in the hook JSON configuration file.
The SERVER_PORT variable is still supported for backward compatibility, although SERVER_PORT_DEFAULT takes precedence if set.SERVER_PORT environment variable in the hook JSON configuration file has been deprecated.
Support for it will be removed in a future release.com.hooks.ssh.pidfile_container OCI annotation, which allows to customize the path to the Dropbear daemon PIDfile inside the container.com.hooks.ssh.pidfile_host OCI annotation, which optionally copies the PIDfile of the Dropbear server to the specified path on the host.OVERLAY_MOUNT_HOME_SSH environment variable, which allows to control the creation of an overlay filesystem on top of the container's ${HOME}/.ssh directory.
More details here.com.hooks.ssh.authorize_ssh_key OCI annotation, which allows to authorize a user-provided public key for connecting to the running container.<registry>/<image>)sarus hooks command to list the hooks configured for the engine--annotation option to sarus run for setting custom annotations in the OCI bundle. More details here
--mpi-type option to sarus run for selecting an MPI hook among those configured by the system administratordefaultMPIType parameter in the sarus.json configuration file. More details here.repositoryMetadataLockTimings parameter in the sarus.json configuration file. More details here.sarus run command.
The aforementioned files are now correctly created or updated with user and group ownership of the user who launched Sarus.mksquashfs through the mksquashfsOptions parameter in the sarus.json configuration filesarus.json configuration filesarus run and sarus images commands now automatically remove images missing the internal SquashFS or metadata file, and report them as not availableconfigure_installation.sh script can now acquire custom values for the local and/or centralized repository paths from environment variables.
More details here
mksquashfsPath parameter in the sarus.json configuration file has been excluded from the security checks.
The mksquashfs utility is only used by sarus pull and sarus load commands, which already run without privilegesdocker.io.
When the server is not entered as part of the image reference, the sarus run command first looks under docker.io repositories and, if the image is not available, falls back to images under the previous default server (index.docker.io). This is done to preserve compatibility with existing workflows.
The sarus images and sarus rmi commands treat images from index.docker.io as images from a 3rd party registry.mediaType property, Sarus now attempts to process the manifest as an OCI Manifest V1 instead of failing with an error.--digests option to sarus images for displaying digests of locally available images--username and --password-stdin options to sarus pull for supplying authentication credentials directly on the command line. More details here
containersPolicy parameter in the sarus.json configuration file. More details here.containersRegistries.dPath parameter in the sarus.json configuration file. More details here.sarus images command now displays the image ID by default.
The image ID, as defined by the OCI Image Specification, is the hash of the image's configuration JSON. More details here.sarus pull command now skips the pull if the requested image is already available locally and up-to-dateinsecureRegistries parameter from sarus.json and the built-in support for insecure registries.
Access to insecure registries via Skopeo must now be enabled through containers-registries.conf(5) files. More details here.