From 1c6c7ffcc8d0ecca987b2ceaa0bb35f4a75268ce Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Thu, 5 Nov 2026 22:24:31 +0100 Subject: [PATCH 1/2] 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. From e2aefc6e1a894e9fa2435e4fad3b70fa3b94d2ad Mon Sep 17 00:00:00 2001 From: Sebastiaan van Stijn Date: Thu, 5 Nov 2026 22:30:44 +0100 Subject: [PATCH 2/2] docs: update examples for ubuntu LTS versions Signed-off-by: Sebastiaan van Stijn --- .../reference/commandline/container_commit.md | 16 ++++---- docs/reference/commandline/container_ls.md | 10 ++--- docs/reference/commandline/image_pull.md | 22 +++++------ docs/reference/commandline/service_create.md | 2 +- docs/reference/commandline/system_events.md | 4 +- docs/reference/run.md | 38 +++++++++---------- man/src/container/ls.md | 4 +- man/src/image/ls.md | 2 +- man/src/image/pull.md | 22 +++++------ man/src/system/events.md | 18 ++++----- man/src/system/info.md | 4 +- 11 files changed, 71 insertions(+), 71 deletions(-) diff --git a/docs/reference/commandline/container_commit.md b/docs/reference/commandline/container_commit.md index 6aab8df4d0..6c0551f698 100644 --- a/docs/reference/commandline/container_commit.md +++ b/docs/reference/commandline/container_commit.md @@ -44,8 +44,8 @@ created. Supported `Dockerfile` instructions: $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -c3f279d17e0a ubuntu:24.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky -197387f1b436 ubuntu:24.04 /bin/bash 7 days ago Up 25 hours focused_hamilton +c3f279d17e0a ubuntu:26.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky +197387f1b436 ubuntu:26.04 /bin/bash 7 days ago Up 25 hours focused_hamilton $ docker commit c3f279d17e0a svendowideit/testimage:version3 @@ -63,8 +63,8 @@ svendowideit/testimage version3 f5283438590d 16 sec $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -c3f279d17e0a ubuntu:24.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky -197387f1b436 ubuntu:24.04 /bin/bash 7 days ago Up 25 hours focused_hamilton +c3f279d17e0a ubuntu:26.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky +197387f1b436 ubuntu:26.04 /bin/bash 7 days ago Up 25 hours focused_hamilton $ docker inspect -f "{{ .Config.Env }}" c3f279d17e0a @@ -85,8 +85,8 @@ $ docker inspect -f "{{ .Config.Env }}" f5283438590d $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -c3f279d17e0a ubuntu:24.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky -197387f1b436 ubuntu:24.04 /bin/bash 7 days ago Up 25 hours focused_hamilton +c3f279d17e0a ubuntu:26.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky +197387f1b436 ubuntu:26.04 /bin/bash 7 days ago Up 25 hours focused_hamilton $ docker commit --change='CMD ["apachectl", "-DFOREGROUND"]' -c "EXPOSE 80" c3f279d17e0a svendowideit/testimage:version4 @@ -100,6 +100,6 @@ $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 89373736e2e7 testimage:version4 "apachectl -DFOREGROU" 3 seconds ago Up 2 seconds 80/tcp distracted_fermat -c3f279d17e0a ubuntu:24.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky -197387f1b436 ubuntu:24.04 /bin/bash 7 days ago Up 25 hours focused_hamilton +c3f279d17e0a ubuntu:26.04 /bin/bash 7 days ago Up 25 hours desperate_dubinsky +197387f1b436 ubuntu:26.04 /bin/bash 7 days ago Up 25 hours focused_hamilton ``` diff --git a/docs/reference/commandline/container_ls.md b/docs/reference/commandline/container_ls.md index bdbff11e70..aa80389686 100644 --- a/docs/reference/commandline/container_ls.md +++ b/docs/reference/commandline/container_ls.md @@ -33,7 +33,7 @@ Running `docker ps --no-trunc` showing 2 linked containers. $ docker ps --no-trunc CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -ca5534a51dd04bbcebe9b23ba05f389466cf0c190f1f8f182d7eea92a9671d00 ubuntu:24.04 bash 17 seconds ago Up 16 seconds 3300-3310/tcp webapp +ca5534a51dd04bbcebe9b23ba05f389466cf0c190f1f8f182d7eea92a9671d00 ubuntu:26.04 bash 17 seconds ago Up 16 seconds 3300-3310/tcp webapp 9ca9747b233100676a48cc7806131586213fa5dab86dd1972d6a8732e3a84a4d crosbymichael/redis:latest /redis-server --dir 33 minutes ago Up 33 minutes 6379/tcp redis,webapp/db ``` @@ -240,13 +240,13 @@ CONTAINER ID IMAGE COMMAND CREATED 919e1179bdb8 ubuntu-c1 "top" About a minute ago Up About a minute admiring_lovelace ``` -Match containers based on the `ubuntu` version `24.04` image: +Match containers based on the `ubuntu` version `26.04` image: ```console -$ docker ps --filter ancestor=ubuntu:24.04 +$ docker ps --filter ancestor=ubuntu:26.04 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -82a598284012 ubuntu:24.04 "top" 3 minutes ago Up 3 minutes sleepy_bose +82a598284012 ubuntu:26.04 "top" 3 minutes ago Up 3 minutes sleepy_bose ``` The following matches containers based on the layer `d0e008c6cf02` or an image @@ -256,7 +256,7 @@ that have this layer in its layer stack. $ docker ps --filter ancestor=d0e008c6cf02 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -82a598284012 ubuntu:24.04 "top" 3 minutes ago Up 3 minutes sleepy_bose +82a598284012 ubuntu:26.04 "top" 3 minutes ago Up 3 minutes sleepy_bose ``` #### Create time diff --git a/docs/reference/commandline/image_pull.md b/docs/reference/commandline/image_pull.md index 05e31246c7..4ced3fb8ad 100644 --- a/docs/reference/commandline/image_pull.md +++ b/docs/reference/commandline/image_pull.md @@ -106,8 +106,8 @@ refer to [understand images, containers, and storage drivers](https://docs.docke So far, you've pulled images by their name (and "tag"). Using names and tags is a convenient way to work with images. When using tags, you can `docker pull` an image again to make sure you have the most up-to-date version of that image. -For example, `docker pull ubuntu:24.04` pulls the latest version of the Ubuntu -24.04 image. +For example, `docker pull ubuntu:26.04` pulls the latest version of the Ubuntu +26.04 image. In some cases you don't want images to be updated to newer versions, but prefer to use a fixed version of an image. Docker enables you to pull an image by its @@ -116,16 +116,16 @@ of an image to pull. Doing so, allows you to "pin" an image to that version, and guarantee that the image you're using is always the same. To know the digest of an image, pull the image first. Let's pull the latest -`ubuntu:24.04` image from Docker Hub: +`ubuntu:26.04` image from Docker Hub: ```console -$ docker pull ubuntu:24.04 +$ docker pull ubuntu:26.04 -24.04: Pulling from library/ubuntu +26.04: Pulling from library/ubuntu 125a6e411906: Pull complete Digest: sha256:2e863c44b718727c860746568e1d54afd13b2fa71b160f5cd9058fc436217b30 -Status: Downloaded newer image for ubuntu:24.04 -docker.io/library/ubuntu:24.04 +Status: Downloaded newer image for ubuntu:26.04 +docker.io/library/ubuntu:26.04 ``` Docker prints the digest of the image after the pull has finished. In the example @@ -213,11 +213,11 @@ shorthand) to see the images that were pulled. The example below shows all the ```console $ docker image ls --filter reference=ubuntu REPOSITORY TAG IMAGE ID CREATED SIZE -ubuntu 22.04 8a3cdc4d1ad3 3 weeks ago 77.9MB -ubuntu jammy 8a3cdc4d1ad3 3 weeks ago 77.9MB -ubuntu 24.04 35a88802559d 6 weeks ago 78.1MB +ubuntu 24.04 8a3cdc4d1ad3 3 weeks ago 77.9MB +ubuntu noble 8a3cdc4d1ad3 3 weeks ago 77.9MB +ubuntu 26.04 35a88802559d 6 weeks ago 78.1MB ubuntu latest 35a88802559d 6 weeks ago 78.1MB -ubuntu noble 35a88802559d 6 weeks ago 78.1MB +ubuntu resolute 35a88802559d 6 weeks ago 78.1MB ``` ### Cancel a pull diff --git a/docs/reference/commandline/service_create.md b/docs/reference/commandline/service_create.md index 0896c6a294..a1d44dd36b 100644 --- a/docs/reference/commandline/service_create.md +++ b/docs/reference/commandline/service_create.md @@ -706,7 +706,7 @@ follows: | `node.platform.os` | Node operating system | `node.platform.os==windows` | | `node.platform.arch` | Node architecture | `node.platform.arch==x86_64` | | `node.labels` | User-defined node labels | `node.labels.security==high` | -| `engine.labels` | Docker Engine's labels | `engine.labels.operatingsystem==ubuntu-24.04` | +| `engine.labels` | Docker Engine's labels | `engine.labels.operatingsystem==ubuntu-26.04` | `engine.labels` apply to Docker Engine labels like operating system, drivers, etc. Swarm administrators add `node.labels` for operational purposes by using diff --git a/docs/reference/commandline/system_events.md b/docs/reference/commandline/system_events.md index 7de1fb61f6..081c140742 100644 --- a/docs/reference/commandline/system_events.md +++ b/docs/reference/commandline/system_events.md @@ -339,8 +339,8 @@ $ docker events --filter 'type=network' $ docker events --filter 'container=container_1' --filter 'container=container_2' -2014-09-03T15:49:29.999999999Z07:00 container die 4386fb97867d (image=ubuntu:24.04) -2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:24.04) +2014-09-03T15:49:29.999999999Z07:00 container die 4386fb97867d (image=ubuntu:26.04) +2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:26.04) 2014-05-10T17:42:14.999999999Z07:00 container die 7805c1d35632 (imager=redis:7.2) 2014-09-03T15:49:29.999999999Z07:00 container stop 7805c1d35632 (image=redis:7.2) diff --git a/docs/reference/run.md b/docs/reference/run.md index 4824233685..c0c8a1a90e 100644 --- a/docs/reference/run.md +++ b/docs/reference/run.md @@ -35,7 +35,7 @@ reference to create or run a container based on an image. An image tag is the image version, which defaults to `latest` when omitted. Use the tag to run a container from specific version of an image. For example, to -run version `24.04` of the `ubuntu` image: `docker run ubuntu:24.04`. +run version `26.04` of the `ubuntu` image: `docker run ubuntu:26.04`. #### Image digests @@ -406,14 +406,14 @@ We have four ways to set user memory usage: Examples: ```console -$ docker run -it ubuntu:24.04 /bin/bash +$ docker run -it ubuntu:26.04 /bin/bash ``` We set nothing about memory, this means the processes in the container can use as much memory and swap memory as they need. ```console -$ docker run -it -m 300M --memory-swap -1 ubuntu:24.04 /bin/bash +$ docker run -it -m 300M --memory-swap -1 ubuntu:26.04 /bin/bash ``` We set memory limit and disabled swap memory limit, this means the processes in @@ -421,7 +421,7 @@ the container can use 300M memory and as much swap memory as they need (if the host supports swap memory). ```console -$ docker run -it -m 300M ubuntu:24.04 /bin/bash +$ docker run -it -m 300M ubuntu:26.04 /bin/bash ``` We set memory limit only, this means the processes in the container can use @@ -430,7 +430,7 @@ We set memory limit only, this means the processes in the container can use would be 2*300M, so processes can use 300M swap memory as well. ```console -$ docker run -it -m 300M --memory-swap 1G ubuntu:24.04 /bin/bash +$ docker run -it -m 300M --memory-swap 1G ubuntu:26.04 /bin/bash ``` We set both memory and swap memory, so the processes in the container can use @@ -456,7 +456,7 @@ The following example limits the memory (`-m`) to 500M and sets the memory reservation to 200M. ```console -$ docker run -it -m 500M --memory-reservation 200M ubuntu:24.04 /bin/bash +$ docker run -it -m 500M --memory-reservation 200M ubuntu:26.04 /bin/bash ``` Under this configuration, when the container consumes memory more than 200M and @@ -466,7 +466,7 @@ memory below 200M. The following example set memory reservation to 1G without a hard memory limit. ```console -$ docker run -it --memory-reservation 1G ubuntu:24.04 /bin/bash +$ docker run -it --memory-reservation 1G ubuntu:26.04 /bin/bash ``` The container can use as much memory as it needs. The memory reservation setting @@ -484,13 +484,13 @@ The following example limits the memory to 100M and disables the OOM killer for this container: ```console -$ docker run -it -m 100M --oom-kill-disable ubuntu:24.04 /bin/bash +$ docker run -it -m 100M --oom-kill-disable ubuntu:26.04 /bin/bash ``` The following example, illustrates a dangerous way to use the flag: ```console -$ docker run -it --oom-kill-disable ubuntu:24.04 /bin/bash +$ docker run -it --oom-kill-disable ubuntu:26.04 /bin/bash ``` The container has unlimited memory which can cause the host to run out memory @@ -510,7 +510,7 @@ between 0 and 100. A value of 0 turns off anonymous page swapping. A value of For example, you can set: ```console -$ docker run -it --memory-swappiness=0 ubuntu:24.04 /bin/bash +$ docker run -it --memory-swappiness=0 ubuntu:26.04 /bin/bash ``` Setting the `--memory-swappiness` option is helpful when you want to retain the @@ -561,7 +561,7 @@ And usually `--cpu-period` should work with `--cpu-quota`. Examples: ```console -$ docker run -it --cpu-period=50000 --cpu-quota=25000 ubuntu:24.04 /bin/bash +$ docker run -it --cpu-period=50000 --cpu-quota=25000 ubuntu:26.04 /bin/bash ``` If there is 1 CPU, this means the container can get 50% CPU worth of run-time every 50ms. @@ -582,13 +582,13 @@ We can set cpus in which to allow execution for containers. Examples: ```console -$ docker run -it --cpuset-cpus="1,3" ubuntu:24.04 /bin/bash +$ docker run -it --cpuset-cpus="1,3" ubuntu:26.04 /bin/bash ``` This means processes in container can be executed on cpu 1 and cpu 3. ```console -$ docker run -it --cpuset-cpus="0-2" ubuntu:24.04 /bin/bash +$ docker run -it --cpuset-cpus="0-2" ubuntu:26.04 /bin/bash ``` This means processes in container can be executed on cpu 0, cpu 1 and cpu 2. @@ -599,14 +599,14 @@ on NUMA systems. Examples: ```console -$ docker run -it --cpuset-mems="1,3" ubuntu:24.04 /bin/bash +$ docker run -it --cpuset-mems="1,3" ubuntu:26.04 /bin/bash ``` This example restricts the processes in the container to only use memory from memory nodes 1 and 3. ```console -$ docker run -it --cpuset-mems="0-2" ubuntu:24.04 /bin/bash +$ docker run -it --cpuset-mems="0-2" ubuntu:26.04 /bin/bash ``` This example restricts the processes in the container to only use memory from @@ -637,8 +637,8 @@ For example, the commands below create two containers with different blkio weight: ```console -$ docker run -it --name c1 --blkio-weight 300 ubuntu:24.04 /bin/bash -$ docker run -it --name c2 --blkio-weight 600 ubuntu:24.04 /bin/bash +$ docker run -it --name c1 --blkio-weight 300 ubuntu:26.04 /bin/bash +$ docker run -it --name c2 --blkio-weight 600 ubuntu:26.04 /bin/bash ``` If you do block IO in the two containers at the same time, by, for example: @@ -854,11 +854,11 @@ For interacting with the network stack, instead of using `--privileged` they should use `--cap-add=NET_ADMIN` to modify the network interfaces. ```console -$ docker run -it --rm ubuntu:24.04 ip link add dummy0 type dummy +$ docker run -it --rm ubuntu:26.04 ip link add dummy0 type dummy RTNETLINK answers: Operation not permitted -$ docker run -it --rm --cap-add=NET_ADMIN ubuntu:24.04 ip link add dummy0 type dummy +$ docker run -it --rm --cap-add=NET_ADMIN ubuntu:26.04 ip link add dummy0 type dummy ``` To mount a FUSE based filesystem, you need to combine both `--cap-add` and diff --git a/man/src/container/ls.md b/man/src/container/ls.md index 013fa9cde0..9c95e541b2 100644 --- a/man/src/container/ls.md +++ b/man/src/container/ls.md @@ -48,10 +48,10 @@ Valid placeholders for the Go template are listed below: $ docker container ls -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES - a87ecb4f327c ubuntu:24.04 /bin/sh -c #(nop) MA 20 minutes ago Exit 0 desperate_brattain + a87ecb4f327c ubuntu:26.04 /bin/sh -c #(nop) MA 20 minutes ago Exit 0 desperate_brattain 01946d9d34d8 busybox /bin/sh -c #(nop) MA 33 minutes ago Exit 0 thirsty_bell c1d3b0166030 acffc0358b9e /bin/sh -c yum -y up 2 weeks ago Exit 1 determined_torvalds - 41d50ecd2f57 ubuntu:24.04 /bin/sh -c #(nop) MA 2 weeks ago Exit 0 drunk_pike + 41d50ecd2f57 ubuntu:26.04 /bin/sh -c #(nop) MA 2 weeks ago Exit 0 drunk_pike ## Display only IDs of all containers, including non-running diff --git a/man/src/image/ls.md b/man/src/image/ls.md index ed1b1d0d78..03bf2e1ed2 100644 --- a/man/src/image/ls.md +++ b/man/src/image/ls.md @@ -10,7 +10,7 @@ The title REPOSITORY for the first title may seem confusing. It is essentially the image name. However, because you can tag a specific image, and multiple tags (image instances) can be associated with a single name, the name is really a repository for all tagged images of the same name. For example consider an image -called ubuntu. It may be tagged with 24.04 or 22.04, etc. to manage different +called ubuntu. It may be tagged with 26.04 or 24.04, etc. to manage different versions. ## Filters diff --git a/man/src/image/pull.md b/man/src/image/pull.md index 7954fc9cf6..50d9d51823 100644 --- a/man/src/image/pull.md +++ b/man/src/image/pull.md @@ -64,8 +64,8 @@ in the online documentation. So far, you've pulled images by their name (and "tag"). Using names and tags is a convenient way to work with images. When using tags, you can `docker image pull` an image again to make sure you have the most up-to-date version of that image. -For example, `docker image pull ubuntu:24.04` pulls the latest version of the Ubuntu -24.04 image. +For example, `docker image pull ubuntu:26.04` pulls the latest version of the Ubuntu +26.04 image. In some cases you don't want images to be updated to newer versions, but prefer to use a fixed version of an image. Docker enables you to pull an image by its @@ -74,15 +74,15 @@ of an image to pull. Doing so, allows you to "pin" an image to that version, and guarantee that the image you're using is always the same. To know the digest of an image, pull the image first. Let's pull the latest -`ubuntu:24.04` image from Docker Hub: +`ubuntu:26.04` image from Docker Hub: - $ docker image pull ubuntu:24.04 + $ docker image pull ubuntu:26.04 - 24.04: Pulling from library/ubuntu + 26.04: Pulling from library/ubuntu 125a6e411906: Pull complete Digest: sha256:2e863c44b718727c860746568e1d54afd13b2fa71b160f5cd9058fc436217b30 - Status: Downloaded newer image for ubuntu:24.04 - docker.io/library/ubuntu:24.04 + Status: Downloaded newer image for ubuntu:26.04 + docker.io/library/ubuntu:26.04 Docker prints the digest of the image after the pull has finished. In the example above, the digest of the image is: @@ -159,11 +159,11 @@ images that are present locally: $ docker image ls --filter reference=ubuntu REPOSITORY TAG IMAGE ID CREATED SIZE - ubuntu 22.04 8a3cdc4d1ad3 3 weeks ago 77.9MB - ubuntu jammy 8a3cdc4d1ad3 3 weeks ago 77.9MB - ubuntu 24.04 35a88802559d 6 weeks ago 78.1MB + ubuntu 24.04 8a3cdc4d1ad3 3 weeks ago 77.9MB + ubuntu noble 8a3cdc4d1ad3 3 weeks ago 77.9MB + ubuntu 26.04 35a88802559d 6 weeks ago 78.1MB ubuntu latest 35a88802559d 6 weeks ago 78.1MB - ubuntu noble 35a88802559d 6 weeks ago 78.1MB + ubuntu resolute 35a88802559d 6 weeks ago 78.1MB ## Cancel a pull diff --git a/man/src/system/events.md b/man/src/system/events.md index 240f7a4dc0..f4539176a9 100644 --- a/man/src/system/events.md +++ b/man/src/system/events.md @@ -62,8 +62,8 @@ The following example outputs all events that were generated in the last 3 minut relative to the current time on the client machine: # docker events --since '3m' - 2015-05-12T11:51:30.999999999Z07:00 4386fb97867d: (from ubuntu:24.04) die - 2015-05-12T15:52:12.999999999Z07:00 4386fb97867d: (from ubuntu:24.04) stop + 2015-05-12T11:51:30.999999999Z07:00 4386fb97867d: (from ubuntu:26.04) die + 2015-05-12T15:52:12.999999999Z07:00 4386fb97867d: (from ubuntu:26.04) stop 2015-05-12T15:53:45.999999999Z07:00 7805c1d35632: (from redis:7.2) die 2015-05-12T15:54:03.999999999Z07:00 7805c1d35632: (from redis:7.2) stop @@ -97,21 +97,21 @@ Lines. For information about JSON Lines, refer to https://jsonlines.org . ## Filters $ docker events --filter 'event=stop' - 2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:24.04) + 2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:26.04) 2014-09-03T17:42:14.999999999Z07:00 container stop 7805c1d35632 (image=redis:7.2) - $ docker events --filter 'image=ubuntu:24.04' - 2014-05-10T17:42:14.999999999Z07:00 container start 4386fb97867d (image=ubuntu:24.04) - 2014-05-10T17:42:14.999999999Z07:00 container die 4386fb97867d (image=ubuntu:24.04) - 2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:24.04) + $ docker events --filter 'image=ubuntu:26.04' + 2014-05-10T17:42:14.999999999Z07:00 container start 4386fb97867d (image=ubuntu:26.04) + 2014-05-10T17:42:14.999999999Z07:00 container die 4386fb97867d (image=ubuntu:26.04) + 2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:26.04) $ docker events --filter 'container=7805c1d35632' 2014-05-10T17:42:14.999999999Z07:00 container die 7805c1d35632 (image=redis:7.2) 2014-09-03T15:49:29.999999999Z07:00 container stop 7805c1d35632 (image= redis:7.2) $ docker events --filter 'container=7805c1d35632' --filter 'container=4386fb97867d' - 2014-09-03T15:49:29.999999999Z07:00 container die 4386fb97867d (image=ubuntu:24.04) - 2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:24.04) + 2014-09-03T15:49:29.999999999Z07:00 container die 4386fb97867d (image=ubuntu:26.04) + 2014-05-10T17:42:14.999999999Z07:00 container stop 4386fb97867d (image=ubuntu:26.04) 2014-05-10T17:42:14.999999999Z07:00 container die 7805c1d35632 (image=redis:7.2) 2014-09-03T15:49:29.999999999Z07:00 container stop 7805c1d35632 (image=redis:7.2) diff --git a/man/src/system/info.md b/man/src/system/info.md index 3d543f0219..a59b4c9277 100644 --- a/man/src/system/info.md +++ b/man/src/system/info.md @@ -71,8 +71,8 @@ Server: seccomp Profile: builtin cgroupns - Kernel Version: 5.15.0-25-generic - Operating System: Ubuntu 22.04 LTS + Kernel Version: 6.8.0-31-generic + Operating System: Ubuntu 24.04 LTS OSType: linux Architecture: x86_64 CPUs: 1