Skip to content

Latest commit

 

History

History
66 lines (46 loc) · 2.6 KB

CollectionsAndArchitectures.rst

File metadata and controls

66 lines (46 loc) · 2.6 KB

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/bookworm based on ARCHITECTURE/debian:bookworm-slim
  • debian/bullseye based on ARCHITECTURE/debian:bullseye-slim (default)
  • rockylinux/8 based on ARCHITECTURE/rockylinux:8

Important

Deprecated:

  • None

Removed:

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

Architectures:

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

.. centered:: |SHIELD:Generic:GCR| |SHIELD:Generic:GHCR|

However, fields ARCHITECURE and COLLECTION are optional because:

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 :ref:`User Guide <UserGuide>` for further details.

Important

The table in :ref:`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.