Collections and architecturesΒΆ

Images in this repository are organised in collections and built for multiple architectures. A collection is a set of images which share a common ancestor; a base layer. Having images with a common ancestor allows reducing bandwidth and disk usage when pulling several of them. See docs.docker.com: About storage drivers | Images and layers.

Collections:

  • debian/bullseye based on ARCHITECTURE/debian:bullseye-slim (default)

  • centos/7 based on ARCHITECTURE/centos:7

Important

Deprecated collections:

  • debian/buster based on ARCHITECTURE/debian:buster-slim

Architectures:

Each image is published to both gcr.io and ghcr.io:

Full image name (GCR) Full image name (GHCR)

However, fields ARCHITECURE and COLLECTION are optional because:

  • Images for the default architecture are mirrored to SHIELD:Mirror:GCR:NoArchitecture and SHIELD:Mirror:GHCR:NoArchitecture.

  • Images of the default collection are mirrored to SHIELD:Mirror:GCR:NoCollection and SHIELD:Mirror:GHCR:NoCollection.

  • Images of the default collection for the default architecture are mirrored to SHIELD:Mirror:Docker.

  • Images of the default collection for the default architecture which are not build or pkg are mirrored to SHIELD:Mirror:GCR:Default and SHIELD:Mirror:GHCR:Default.

Important

Image names and tags in this documentation are provided without the registry prefix. Hence, one of the prefixes listed above needs to be used when actually pulling/using the images. See User Guide for further details.

Important

The table in Tools and images shows the tools available in the default collection for the default architecture. Some tools are available in a subset of collections or for a subset of architectures only. Browse the registries and/or the Continuous Integration workflows for finding images available in collections other than the default.