Reproducible computational environments using containers: Introduction to Singularity: Glossary

Singularity is another container platform and it is often used in cluster/HPC/research environments.

Singularity has a different security model to other container platforms, one of the key reasons that it is well suited to HPC and cluster environments.

Singularity has its own container image format (SIF).

The singularity command can be used to pull images from Singularity Hub and run a container from an image file.

Singularity caches downloaded images so that an unchanged image isn’t downloaded again when it is requested using the singularity pull command.

You can free up space in the cache by removing all locally cached images or by specifying individual images to remove.

The singularity exec is an alternative to singularity run that allows you to start a container running a specific command.

The singularity shell command can be used to start a container and run an interactive shell within it.

Your current directory and home directory are usually available by default in a container.

You have the same username and permissions in a container as on the host system.

You can specify additional host system directories to be available in the container.

Singularity can start a container from a Docker image which can be pulled directly from Docker Hub.

You can build container images using Docker and run them using Singularity.

You must build the Docker container image with the correct processor architecture to match your remote HPC system.

Dockerhub makes it easier to transfer container images from your local system to a remote HPC system.

Singularity images containing MPI applications can be built on one platform and then run on another (e.g. an HPC cluster) if the two platforms have compatible MPI implementations.

When running an MPI application within a Singularity container, use the MPI executable on the host system to launch a Singularity container for each process.

Think about parallel application performance requirements and how where you build/run your image may affect that.