docs: deprecated: complete deprecation of kernel-memory limit

Signed-off-by: Sebastiaan van Stijn <[email protected]>

Author: thaJeztah

docs/deprecated.md

@@ -730,25 +730,11 @@ When using cgroups v2, the `--blkio-weight` options are implemented using
 
 Specifying kernel memory limit (`docker run --kernel-memory`) is no longer supported
 because the [Linux kernel deprecated `kmem.limit_in_bytes` in v5.4](https://github.com/torvalds/linux/commit/0158115f702b0ba208ab0b5adf44cae99b3ebcc7).
-The OCI runtime specification now marks this option (as well as `--kernel-memory-tcp`)
-as ["NOT RECOMMENDED"](https://github.com/opencontainers/runtime-spec/pull/1093),
+The OCI runtime specification now marks this option as ["NOT RECOMMENDED"](https://github.com/opencontainers/runtime-spec/pull/1093),
 and OCI runtimes such as `runc` no longer support this option.
 
-Docker API v1.42 and up now ignores this option when set. Older versions of the
-API continue to accept the option, but depending on the OCI runtime used, may
-take no effect.
-
-> [!NOTE]
-> While not deprecated (yet) in Docker, the OCI runtime specification also
-> deprecated the `memory.kmem.tcp.limit_in_bytes` option. When using `runc` as
-> runtime, this option takes no effect. The Linux kernel did not explicitly
-> deprecate this feature, and there is a tracking ticket in the `runc` issue
-> tracker to determine if this option should be reinstated or if this was an
-> oversight of the Linux kernel maintainers (see [opencontainers/runc#3174](https://github.com/opencontainers/runc/issues/3174)).
->
-> The `memory.kmem.tcp.limit_in_bytes` option is only supported with cgroups v1,
-> and not available on installations running with cgroups v2. This option is
-> only supported by the API, and not exposed on the `docker` command-line.
+The Docker API no longer handles the kernel-memory fields, and Docker CLI v29.0
+removes the `--kernel-memory` option.
 
 ### Classic Swarm and overlay networks using cluster store