From 6468c63c81aa55c21e75076494f3ec11f1e09916 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Thu, 23 Nov 2023 23:21:07 +0100 Subject: [PATCH] docs: update debian examples to use bookworm "bullseye" is no longer the "latest" debian, so these examples were now incorrect. Signed-off-by: Sebastiaan van Stijn --- docs/reference/commandline/pull.md | 16 ++++++++-------- man/src/image/pull.md | 16 ++++++++-------- 2 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/reference/commandline/pull.md b/docs/reference/commandline/pull.md index 8c90dc4e5d..c1465f8770 100644 --- a/docs/reference/commandline/pull.md +++ b/docs/reference/commandline/pull.md @@ -67,18 +67,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:bullseye` image shares -its layer with the `debian:latest`. Pulling the `debian:bullseye` image therefore +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 only pulls its metadata, but not its layers, because the layer is already present locally: ```console -$ docker image pull debian:bullseye +$ docker image pull debian:bookworm -bullseye: Pulling from library/debian +bookworm: Pulling from library/debian Digest: sha256:3f1d6c17773a45c97bd8f158d665c9709d7b29ed7917ac934086ad96f92e4510 -Status: Downloaded newer image for debian:bullseye -docker.io/library/debian:bullseye +Status: Downloaded newer image for debian:bookworm +docker.io/library/debian:bookworm ``` To see which images are present locally, use the [`docker images`](images.md) @@ -88,13 +88,13 @@ command: $ docker images REPOSITORY TAG IMAGE ID CREATED SIZE -debian bullseye 4eacea30377a 8 days ago 124MB +debian bookworm 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:bullseye` and `debian:latest` have the same image ID because they are +`debian:bookworm` 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 7b6f1f2a40..8187ede1e8 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:bullseye` image shares -its layer with the `debian:latest`. Pulling the `debian:bullseye` image therefore +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 only pulls its metadata, but not its layers, because the layer is already present locally: - $ docker image pull debian:bullseye + $ docker image pull debian:bookworm - bullseye: Pulling from library/debian + bookworm: Pulling from library/debian Digest: sha256:3f1d6c17773a45c97bd8f158d665c9709d7b29ed7917ac934086ad96f92e4510 - Status: Downloaded newer image for debian:bullseye - docker.io/library/debian:bullseye + Status: Downloaded newer image for debian:bookworm + docker.io/library/debian:bookworm 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 bullseye 4eacea30377a 8 days ago 124MB + debian bookworm 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:bullseye` and `debian:latest` have the same image ID because they are +`debian:bookworm` 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.