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/trixie based on ARCHITECTURE/debian:trixie-slim (default)

• rockylinux/8 based on ARCHITECTURE/rockylinux:8

Important

Deprecated:

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

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

Removed:

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

• centos/7 based on ARCHITECTURE/centos:7

Architectures:

• amd64 (default)

• arm32v7

• arm64v8

• ppc64le

• s390x

• mips64le

• riscv64

Each image is published to ghcr.io:

However, fields ARCHITECURE and COLLECTION are optional because:

• All images for the default architecture and all images of the default collection are pushed to and , respectively.

• Images of the default collection for the default architecture are pushed to and .

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.