From a52e4bb8d846a40bd89dad8d4c198d9ccd19384a Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 22 Apr 2026 03:14:54 +0000
Subject: [PATCH] cli: sync docs with docker/cli v29.4.1

---
 data/cli/engine/docker_container_update.yaml | 42 --------------------
 1 file changed, 42 deletions(-)

diff --git a/data/cli/engine/docker_container_update.yaml b/data/cli/engine/docker_container_update.yaml
index a0dc5196ae67..0fd29551a198 100644
--- a/data/cli/engine/docker_container_update.yaml
+++ b/data/cli/engine/docker_container_update.yaml
@@ -8,11 +8,6 @@ long: |-
     limits on a single container or on many. To specify more than one container,
     provide space-separated list of container names or IDs.
 
-    With the exception of the `--kernel-memory` option, you can specify these
-    options on a running or a stopped container. On kernel version older than
-    4.6, you can only update `--kernel-memory` on a stopped container or on
-    a running container with kernel memory initialized.
-
     > [!WARNING]
     > The `docker update` and `docker container update` commands are not supported
     > for Windows containers.
@@ -118,7 +113,6 @@ options:
       value_type: bytes
       default_value: "0"
       description: Kernel memory limit (deprecated)
-      details_url: '#kernel-memory'
       deprecated: true
       hidden: true
       experimental: false
@@ -210,42 +204,6 @@ examples: |-
     $ docker update --cpu-shares 512 -m 300M abebf7571666 hopeful_morse
     ```
 
-    ### Update a container's kernel memory constraints (--kernel-memory) {#kernel-memory}
-
-    You can update a container's kernel memory limit using the `--kernel-memory`
-    option. On kernel version older than 4.6, this option can be updated on a
-    running container only if the container was started with `--kernel-memory`.
-    If the container was started without `--kernel-memory` you need to stop
-    the container before updating kernel memory.
-
-    > [!NOTE]
-    > The `--kernel-memory` option has been deprecated since Docker 20.10.
-
-    For example, if you started a container with this command:
-
-    ```console
-    $ docker run -dit --name test --kernel-memory 50M ubuntu bash
-    ```
-
-    You can update kernel memory while the container is running:
-
-    ```console
-    $ docker update --kernel-memory 80M test
-    ```
-
-    If you started a container without kernel memory initialized:
-
-    ```console
-    $ docker run -dit --name test2 --memory 300M ubuntu bash
-    ```
-
-    Update kernel memory of running container `test2` will fail. You need to stop
-    the container before updating the `--kernel-memory` setting. The next time you
-    start it, the container uses the new value.
-
-    Kernel version newer than (include) 4.6 does not have this limitation, you
-    can use `--kernel-memory` the same way as other options.
-
     ### Update a container's restart policy (--restart) {#restart}
 
     You can change a container's restart policy on a running container. The new