Maintaining Open Source Singularity Since 2017
Remote Building with OCI Registries
By Adam Hughes
This blog post will demonstrate how to use a definition file in a remote build that references an Open Container Initiative (OCI) image stored in Singularity Enterprise and Singularity Container Services.
First, create an account in Singularity Container Service. To do this, please go to the registration page and click on the “Sign Up” button to obtain free access to the remote builder.
Secondly, using Crane, copy the Docker image over to Singularity Container Service:
$ singularity remote get-login-password | \
crane auth login -u USERNAME --password-stdin \
registry.sylabs.io
2023/06/07 01:56:04 logged in via /home/USERNAME/.docker/config.json
$ crane cp docker.io/ubuntu:23.04 \
registry.sylabs.io/USERNAME/ubuntu/ubuntu:23.04
Then, in the definition file you can reference that OCI image as follows, the
%post instructions are for demonstration purposes only:Bootstrap: docker
From: registry.sylabs.io/USERNAME/ubuntu/ubuntu:23.04
%post
apt update -qq
apt install -y --no-install-recommends \
software-properties-common dirmngr wgetThen you can trigger a remote build either from the remote builder or from the command line:
$ singularity build --remote ubuntu.sif ubuntu.def
INFO: Starting build...
INFO: Setting maximum build duration to 20m0s
INFO: Remote "registry.sylabs.io" added.
INFO: Access Token Verified!
INFO: Token stored in /root/.singularity/remote.yaml
INFO: Remote "registry.sylabs.io" now in use.
INFO: Starting build...
Getting image source signatures
Copying blob sha256:361237ddf3...18f0b3435
Copying config sha256:d710383bdc8e0a...394af54773632
Writing manifest to image destination
Storing signatures
2023/06/07 08:47:51 info unpack layer: sha256:361237dd...b47ccd30556a7ba97c218f0b3435
INFO: Running post scriptlet
...
INFO: Creating SIF file...
INFO: Build complete: /tmp/image-1838580909
INFO: Performing post-build operations
INFO: Generating SBOM for /tmp/image-1838580909
INFO: Adding SBOM to SIF
INFO: Calculating SIF image checksum
INFO: Uploading image to library...
WARNING: Skipping container verification
INFO: Uploading 102181239 bytes
INFO: Image uploaded successfully.
INFO: Build complete: ubuntu.sif
As demonstrated, it is very easy to take a base image from an OCI registry and add more functions in a definition file and obtain a SIF file ready to run in an HPC scheduler.
Join Our Mailing List
Recent Posts
Related Posts
Ensuring Singularity Enterprise Continuity: Crafting a Disaster Recovery Plan
In the dynamic world of IT operations, disaster recovery procedures stand as the secret weapon, quietly ensuring the resilience and continuity of businesses. Whether it's a natural disaster, a cyberattack, or a hardware failure, having a robust disaster recovery plan...
SingularityCE and PRO 4.1: Embracing Compatibility with Dockerfiles
Introduction In the ever-evolving landscape of containerization, where innovation thrives and technological boundaries are pushed, adaptability is key. The ability to seamlessly integrate diverse technologies not only fosters a collaborative ecosystem but also...
OCI Basics using Singularity Enterprise Registry
Overview Singularity Enterprise comes with a fully compliant Open Container Initiative (OCI) registry. The following is a collection of typical registry operations within your workflow. Assuming the Singularity Enterprise registry address is registry.sylabs.io, please...