With the release of v3.0.0
, we're introducing a new changelog format in an attempt to consolidate the information presented in the changelog. The new changelog is reduced in scope to only documenting functionality changes from version to version. This ensures that the changelog is as useful as it can be. Changes which should be documented include:
- Renamed commands
- Deprecated / removed commands
- Changed defaults / behaviors
- Migration guidance
- New features / functionalities
The old changelog can be found in the release-2.6
branch
- New support for building and running encrypted containers with RSA keys and passphrases
--pem-path
option added to thebuild
and action commands for RSA based encrypted containers--passphrase
option added tobuild
and action commands for passphrase based encrypted containersSINGULARITY_ENCRYPTION_PEM_PATH
andSINGULARITY_ENCRYPTION_PASSPHRASE
environment variables added to serve same functions as above--encyrpt
option added tobuild
command to build an encrypted container when environment variables contain a secret
- New
--disable-cache
flag prevents caching of downloaded containers - Added support for multi-line variables in singularity def-files
- Added support for 'indexed' def-file variables (like arrays)
- Added support for SUSE SLE Products
- Added the def-file variables: product, user, regcode, productpgp, registerurl, modules, otherurl (indexed)
- Support multiple-architecture tags in the SCS library
- Added a
--dry-run
flag tocache clean
- Added a
SINGULARITY_SYPGPDIR
environment variable to specify the location of PGP key data - Added a
--nonet
option to the action commands to disable networking when running with the--vm
option - Added a
--long-list
flag to thekey search
command to preserve - Added experimental, hidden
--fusemount
flag to pass a command to mount a libfuse3 based file system within the container
- Runtime now properly honors
SINGULARITY_DISABLE_CACHE
environment variable remote add
command now automatically attempts to login and a--no-login
flag is added to disable this behavior- Using the
pull
command to download an unsigned container no longer produces an error code cache clean
command now prompts user before cleaning when run without--force
option and is more verbose- Shortened the default output of the
key search
command
- The
--allow-unsigned
flag topull
has been deprecated and will be removed in the future
- Remote login and status commands will now use the default remote if a remote name is not supplied
- Added Singularity hub (
shub
) cache support when using thepull
command - Clean cache in a safer way by only deleting the cache subdirectories
- Improvements to the
cache clean
command
- new
oras
URI for pushing and pulling SIF files to and from supported OCI registries - added the
--fakeroot
option tobuild
,exec
,run
,shell
,test
, andinstance start
commands to run container in a new user namespace as uid 0 - added the
fakeroot
network type for use with the--network
option sif
command to allow for the inspection and manipulation of SIF files with the following subcommandsadd
Add a data object to a SIF filedel
Delete a specified object descriptor and data from SIF filedump
Extract and output data objects from SIF filesheader
Display SIF global headersinfo
Display detailed information of object descriptorslist
List object descriptors from SIF filesnew
Create a new empty SIF image filesetprim
Set primary system partition
- This point release fixes the following bugs:
- Allows users to join instances with non-suid workflow
- Removes false warning when seccomp is disabled on the host
- Fixes an issue in the terminal when piping output to commands
- Binds NVIDIA persistenced socket when
--nv
is invoked
- Instance files are now stored in user's home directory for privacy and many checks have been added to ensure that a user can't manipulate files to change
starter-suid
behavior when instances are joined (many thanks to Matthias Gerstner from the SUSE security team for finding and securely reporting this vulnerability)
- Introduced a new basic framework for creating and managing plugins
- Added the ability to create containers through multi-stage builds
- Definitions now require
Bootstrap
be the first parameter of header
- Definitions now require
- Created the concept of a Sylabs Cloud "remote" endpoint and added the ability for users and admins to set them through CLI and conf files
- Added caching for images from Singularity Hub
- Made it possible to compile Singularity outside of
$GOPATH
- Added a json partition to SIF files for OCI configuration when building from an OCI source
- Full integration with Singularity desktop for MacOS code base
-
Introduced the
plugin
command group for creating and managing pluginscompile
Compile a singularity plugindisable
disable an installed singularity pluginenable
Enable an installed singularity plugininspect
Inspect a singularity plugin (either an installed one or an image)install
Install a singularity pluginlist
List installed singularity pluginsuninstall
Uninstall removes the named plugin from the system
-
Introduced the
remote
command group to support management of Singularity endpoints:add
Create a new Sylabs Cloud remote endpointlist
List all remote endpoints that are configuredlogin
Log into a remote endpoint using an authentication tokenremove
Remove an existing Sylabs Cloud remote endpointstatus
Check the status of the services at an endpointuse
Set a remote endpoint to be used by default
-
Added to the
key
command group to improve PGP key management:export
Export a public or private key into a specific fileimport
Import a local key into the local keyringremove
Remove a local public key
-
Added the
Stage: <name>
keyword to the definition file header and thefrom <stage name>
option/argument pair to the%files
section to support multistage builds
- The
--token/-t
option has been deprecated in favor of thesingularity remote
command group
- Ask to confirm password on a newly generated PGP key
- Prompt to push a key to the KeyStore when generated
- Refuse to push an unsigned container unless overridden with
--allow-unauthenticated/-U
option - Warn and prompt when pulling an unsigned container without the
--allow-unauthenticated/-U
option Bootstrap
must now be the first field of every header because of parser requirements for multi-stage builds
- New hidden
buildcfg
command to display compile-time parameters - Added support for
LDFLAGS
,CFLAGS
,CGO_
variables in build system - Added
--nocolor
flag to Singularity client to disable color in logging
singularity capability <add/drop> --desc
has been removedsingularity capability list <--all/--group/--user>
flags have all been removed
- The
--builder
flag to thebuild
command implicitly sets--remote
- Repeated binds no longer cause Singularity to exit and fail, just warn instead
- Corrected typos and improved docstrings throughout
- Removed warning when CWD does not exist on the host system
- Added support to spec file for RPM building on SLES 11
- Introduced the
oci
command group to support a new OCI compliant variant of the Singularity runtime:attach
Attach console to a running container processcreate
Create a container from a bundle directorydelete
Delete containerexec
Execute a command within containerkill
Kill a containermount
Mount create an OCI bundle from SIF imagepause
Suspends all processes inside the containerresume
Resumes all processes previously paused inside the containerrun
Create/start/attach/delete a container from a bundle directorystart
Start container processstate
Query state of a containerumount
Umount delete bundleupdate
Update container cgroups resources
- Added
cache
command group to inspect and manage cached filesclean
Clean your local Singularity cachelist
List your local Singularity cache
- Can now build CLI on darwin for limited functionality on Mac
- Added the
scratch
bootstrap agent to build from anything - Reintroduced support for zypper bootstrap agent
- Added the ability to overwrite a new
singularity.conf
when building from RPM if desired - Fixed several regressions and omissions in SCIF support
- Added caching for containers pulled/built from the Container Library
- Changed
keys
command group tokey
(retained hiddenkeys
command for backward compatibility) - Created an
RPMPREFIX
variable to allow RPMs to be installed in custom locations - Greatly expanded CI unit and end-to-end testing
- Bind paths in
singularity.conf
are properly parsed and applied at runtime - Singularity runtime will properly fail if
singularity.conf
file is not owned by the root user - Several improvements to RPM packaging including using golang from epel, improved support for Fedora, and avoiding overwriting conf file on new RPM install
- Unprivileged
--contain
option now properly mountsdevpts
on older kernels - Uppercase proxy environment variables are now rightly respected
- Add http/https protocols for singularity run/pull commands
- Update to SIF 1.0.2
- Add noPrompt parameter to
pkg/signing/Verify
function to enable silent verification
- Added the
--docker-login
flag to enable interactive authentication with docker registries - Added support for pulling directly from HTTP and HTTPS
- Made minor improvements to RPM packaging and added basic support for alpine packaging
- The
$SINGULARITY_NOHTTPS
,$SINGULARITY_TMPDIR
, and$SINGULARITY_DOCKER_USERNAME
/$SINGULARITY_DOCKER_PASSWORD
environment variables are now correctly respected - Pulling from a private shub registry now works as expected
- Running a container with
--network="none"
no longer incorrectly fails with an error message - Commands now correctly return 1 when incorrectly executed without arguments
- Progress bars no longer incorrectly display when running with
--quiet
or--silent
- Contents of
91-environment.sh
file are now displayed if appropriate when runninginspect --environment
- Improved RPM packaging procedure via makeit
- Enhanced general stability of runtime
- Singularity is now written primarily in Go to bring better integration with the existing container ecosystem
- Added support for new URIs (
build
&run/exec/shell/start
):library://
- Supports the Sylabs.io Cloud Librarydocker-daemon:
- Supports images managed by the locally running docker daemondocker-archive:
- Supports archived docker imagesoci:
- Supports oci imagesoci-archive:
- Supports archived oci images
- Handling of
docker
&oci
URIs/images now utilizes containers/image to parse and convert those image types in a supported way - Replaced
singularity instance.*
command group withsingularity instance *
- The command
singularity help
now only provides help regarding the usage of thesingularity
command. To display an image'shelp
message, usesingularity run-help <image path>
instead
- Removed deprecated
singularity image.*
command group - Removed deprecated
singularity create
command - Removed deprecated
singularity bootstrap
command - Removed deprecated
singularity mount
command
- Added
singularity run-help <image path>
command to output an image'shelp
message - Added
singularity sign <image path>
command to allow a user to cryptographically sign a SIF image - Added
singularity verify <image path>
command to allow a user to verify a SIF image's cryptographic signatures - Added
singularity keys
command to allow the management ofOpenPGP
key stores - Added
singularity capability
command to allow fine grained control over the capabilities of running containers - Added
singularity push
command to push images to the Sylabs.io Cloud Library
- Added flags:
--add-caps <string>
: Run the contained process with the specified capability set (requires root)--allow-setuid
: Allows setuid binaries to be mounted into the container (requires root)--apply-cgroups <path>
: Apply cgroups configuration from file to contained processes (requires root)--dns <string>
: Adds the comma separated list of DNS servers to the containersresolv.conf
file--drop-caps <string>
: Drop the specified capabilities from the container (requires root)--fakeroot
: Run the container in a user namespace asuid=0
. Requires a recent kernel to function properly--hostname <string>
: Set the hostname of the container--keep-privs
: Keep root user privilege inside the container (requires root)--network <string>
: Specify a list of comma separated network types (CNI Plugins) to be present inside the container, each with its own dedicated interface in the container--network-args <string>
: Specify arguments to pass to CNI network plugins (set by--network
)--no-privs
: Drop all privileges from root user inside the container (requires root)--security <string>
: Configure security features such as SELinux, Apparmor, Seccomp...--writable-tmpfs
: Run container with atmpfs
overlay
- The command
singularity instance start
now supports the--boot
flag to boot the container via/sbin/init
- Changes to image mounting behavior:
- All image formats are mounted as read only by default
--writable
only works on images which can be mounted in read/write [applicable to:sandbox
and legacyext3
images]--writable-tmpfs
runs the container with a writabletmpfs
-based overlay [applicable to: all image formats]--overlay <string>
now specifies a list ofext3
/sandbox
images which are set as the containers overlay [applicable to: all image formats]
- All images are now built as Singularity Image Format (SIF) images by default
- When building to a path that already exists,
singularity build
will now prompt the user if they wish to overwrite the file existing at the specified location - The
-w|--writable
flag has been removed - The
-F|--force
flag now overrides the interactive prompt and will always attempt to overwrite the file existing at the specified location - The
-u|--update
flag has been added to support the workflow of running a definition file on top of an existing container [implies--sandbox
, only supportssandbox
image types] - The
singularity build
command now supports the following flags for integration with the Sylabs.io Cloud Library:-r|--remote
: Build the image remotely on the Sylabs Remote Builder (currently unavailable)-d|--detached
: Detach from thestdout
of the remote build [requires--remote
]--builder <string>
: Specifies the URL of the remote builder to access--library <string>
: Specifies the URL of the Sylabs.io Cloud Library to push the built image to when the build command destination is in the formlibrary://<reference>
- The
bootstrap
keyword in the definition file now supports the following values:library
docker-daemon
docker-archive
oci
oci-archive
- The
from
keyword in the definition file now correctly parses adocker
URI which includes theregistry
and/ornamespace
components - The
registry
andnamespace
keywords in the definition file are no longer supported. Instead, those values may all go into thefrom
keyword - Building from a tar archive of a
sandbox
no longer works