From 1c6c7ffcc8d0ecca987b2ceaa0bb35f4a75268ce Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Thu, 5 Nov 2026 22:24:31 +0100 Subject: [PATCH] docs: update examples to use debian trixie Signed-off-by: Sebastiaan van Stijn --- docs/reference/commandline/image_pull.md | 16 ++++++++-------- man/src/image/pull.md | 16 ++++++++-------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/reference/commandline/image_pull.md b/docs/reference/commandline/image_pull.md index beb270660a..05e31246c7 100644 --- a/docs/reference/commandline/image_pull.md +++ b/docs/reference/commandline/image_pull.md @@ -66,18 +66,18 @@ docker.io/library/debian:latest Docker images can consist of multiple layers. In the example above, the image consists of a single layer; `e756f3fdd6a3`. -Layers can be reused by images. For example, the `debian:bookworm` image shares -its layer with the `debian:latest`. Pulling the `debian:bookworm` image therefore +Layers can be reused by images. For example, the `debian:trixie` image shares +its layer with the `debian:latest`. Pulling the `debian:trixie` image therefore only pulls its metadata, but not its layers, because the layer is already present locally: ```console -$ docker image pull debian:bookworm +$ docker image pull debian:trixie -bookworm: Pulling from library/debian +trixie: Pulling from library/debian Digest: sha256:3f1d6c17773a45c97bd8f158d665c9709d7b29ed7917ac934086ad96f92e4510 -Status: Downloaded newer image for debian:bookworm -docker.io/library/debian:bookworm +Status: Downloaded newer image for debian:trixie +docker.io/library/debian:trixie ``` To see which images are present locally, use the [`docker images`](image_ls.md) @@ -87,13 +87,13 @@ command: $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE -debian bookworm 4eacea30377a 8 days ago 124MB +debian trixie 4eacea30377a 8 days ago 124MB debian latest 4eacea30377a 8 days ago 124MB ``` Docker uses a content-addressable image store, and the image ID is a SHA256 digest covering the image's configuration and layers. In the example above, -`debian:bookworm` and `debian:latest` have the same image ID because they are +`debian:trixie` and `debian:latest` have the same image ID because they are the same image tagged with different names. Because they are the same image, their layers are stored only once and do not consume extra disk space. diff --git a/man/src/image/pull.md b/man/src/image/pull.md index caba00938c..7954fc9cf6 100644 --- a/man/src/image/pull.md +++ b/man/src/image/pull.md @@ -27,17 +27,17 @@ Docker Engine uses the `:latest` tag as a default. This example pulls the Docker images can consist of multiple layers. In the example above, the image consists of a single layer; `e756f3fdd6a3`. -Layers can be reused by images. For example, the `debian:bookworm` image shares -its layer with the `debian:latest`. Pulling the `debian:bookworm` image therefore +Layers can be reused by images. For example, the `debian:trixie` image shares +its layer with the `debian:latest`. Pulling the `debian:trixie` image therefore only pulls its metadata, but not its layers, because the layer is already present locally: - $ docker image pull debian:bookworm + $ docker image pull debian:trixie - bookworm: Pulling from library/debian + trixie: Pulling from library/debian Digest: sha256:3f1d6c17773a45c97bd8f158d665c9709d7b29ed7917ac934086ad96f92e4510 - Status: Downloaded newer image for debian:bookworm - docker.io/library/debian:bookworm + Status: Downloaded newer image for debian:trixie + docker.io/library/debian:trixie To see which images are present locally, use the **docker-images(1)** command: @@ -45,12 +45,12 @@ command: $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE - debian bookworm 4eacea30377a 8 days ago 124MB + debian trixie 4eacea30377a 8 days ago 124MB debian latest 4eacea30377a 8 days ago 124MB Docker uses a content-addressable image store, and the image ID is a SHA256 digest covering the image's configuration and layers. In the example above, -`debian:bookworm` and `debian:latest` have the same image ID because they are +`debian:trixie` and `debian:latest` have the same image ID because they are the *same* image tagged with different names. Because they are the same image, their layers are stored only once and do not consume extra disk space.