Singularity was removed from TOSS beginning with version 4.8-13 which is currently rolling out to LC systems. This is due to a combination of security concerns and technical limitations. LC users are encouraged to migrate their existing Singularity workflows to Podman. If you require assistance with migration, please reach out to lc-containers@llnl.gov
We have documentation available for podman usage:
Building containers: https://hpc.llnl.gov/documentation/user-guides/using-containers-lc-hpc-systems/containers-how-build-container
Running containers: https://hpc.llnl.gov/documentation/user-guides/using-containers-lc-hpc-systems/containers-how-interact-container
Migration Quick Guide
Before working with podman, you will need to run the enable-podman command.
Pull an image from a Docker registry with Singularity and converting it to SIF format before running it:
singularity build image.sif docker://path/to/image:version
singularity run image.sif …With podman:
podman run --rm path/to/image:version
Alternatively, if you need to save a Docker image from a Docker registry to disk before running it:
skopeo copy docker://path/to/image:version docker-archive:/path/to/image.tar
podman run --rm docker-archive:/path/to/image.tar ...
Run an image from a Docker archive with Singularity:
singularity run docker-archive:/path/to/image.tar …
With podman:
podman run --rm docker-archive:/path/to/image.tar ...
Running a Singularity image in SIF format:
singularity run /path/to/image.sif ...
With podman:
podman run --rm sif:/path/to/image.sifNote Podman doesn’t use Singularity run scripts so you may need to add the appropriate command to run inside the container manually.
Building a Singularity image from a Singularity definition file:
Please contact lc-containers@llnl.gov for assistance with this.