refactor: Docker Engine manuals section

_vendor/modules.txt

@@ -1,6 +1,6 @@
 # github.com/moby/moby v27.0.3+incompatible
 # github.com/moby/buildkit v0.15.1
 # github.com/docker/buildx v0.16.2
-# github.com/docker/cli v27.0.3+incompatible
+# github.com/docker/cli v27.1.1+incompatible
 # github.com/docker/compose/v2 v2.29.1
 # github.com/docker/scout-cli v1.13.0

content/build/builders/_index.md

@@ -18,7 +18,7 @@ for your builds. This builder uses the BuildKit library bundled with the
 daemon. This builder requires no configuration.
 
 The default builder is directly bound to the Docker daemon and its
-[context](../../engine/context/working-with-contexts.md). If you change the
+[context](/engine/manage-resources/contexts.md). If you change the
 Docker context, your `default` builder refers to the new Docker context.
 
 ## Build drivers

content/build/building/annotations.md

@@ -211,5 +211,5 @@ Reference information:
 [config]: https://github.com/opencontainers/image-spec/blob/main/config.md
 [descriptors]: https://github.com/opencontainers/image-spec/blob/main/descriptor.md
 [indexes]: https://github.com/opencontainers/image-spec/blob/main/image-index.md
-[labels]: ../../config/labels-custom-metadata.md
+[labels]: /engine/manage-resources/labels.md
 [manifests]: https://github.com/opencontainers/image-spec/blob/main/manifest.md

content/build/building/best-practices.md

@@ -145,14 +145,14 @@ database, and an in-memory cache in a decoupled manner.
 
 Limiting each container to one process is a good rule of thumb, but it's not a
 hard and fast rule. For example, not only can containers be
-[spawned with an init process](../../engine/reference/run.md#specify-an-init-process),
+[spawned with an init process](/engine/containers/run.md#specify-an-init-process),
 some programs might spawn additional processes of their own accord. For
 instance, [Celery](https://docs.celeryproject.org/) can spawn multiple worker
 processes, and [Apache](https://httpd.apache.org/) can create one process per
 request.
 
 Use your best judgment to keep containers as clean and modular as possible. If
-containers depend on each other, you can use [Docker container networks](../../network/index.md)
+containers depend on each other, you can use [Docker container networks](/engine/network/_index.md)
 to ensure that these containers can communicate.
 
 ## Sort multi-line arguments
@@ -308,10 +308,10 @@ LABEL vendor=ACME\ Incorporated \
       com.example.release-date="2015-02-12"
 ```
 
-See [Understanding object labels](../../config/labels-custom-metadata.md)
+See [Understanding object labels](/engine/manage-resources/labels.md)
 for guidelines about acceptable label keys and values. For information about
 querying labels, refer to the items related to filtering in
-[Managing labels on objects](../../config/labels-custom-metadata.md#manage-labels-on-objects).
+[Managing labels on objects](/engine/manage-resources/labels.md#manage-labels-on-objects).
 See also [LABEL](../../reference/dockerfile.md#label) in the Dockerfile reference.
 
 ### RUN

content/build/drivers/docker-container.md

@@ -46,11 +46,11 @@ pass to `--driver-opt`:
 | `default-load`   | Boolean | `false`          | Automatically load images to the Docker Engine image store.                                                            |
 | `network`        | String  |                  | Sets the network mode for the container.                                                                               |
 | `cgroup-parent`  | String  | `/docker/buildx` | Sets the cgroup parent of the container if Docker is using the "cgroupfs" driver.                                      |
-| `restart-policy` | String  | `unless-stopped` | Sets the container's [restart policy](../../config/containers/start-containers-automatically.md#use-a-restart-policy). |
+| `restart-policy` | String  | `unless-stopped` | Sets the container's [restart policy](/engine/containers/start-containers-automatically.md#use-a-restart-policy).      |
 | `env.<key>`      | String  |                  | Sets the environment variable `key` to the specified `value` in the container.                                         |
 
 Before you configure the resource limits for the container,
-read about [configuring runtime resource constraints for containers](../../config/containers/resource_constraints/).
+read about [configuring runtime resource constraints for containers](/engine/containers/resource_constraints/).
 
 ## Usage
 

content/build/guide/mounts.md

@@ -215,7 +215,7 @@ mounts.
 Related information:
 
 - [Dockerfile reference](../../reference/dockerfile.md#run---mount)
-- [Bind mounts](../../storage/bind-mounts.md)
+- [Bind mounts](/engine/storage/bind-mounts.md)
 
 ## Next steps
 

content/build/guide/multi-platform.md

@@ -241,7 +241,7 @@ Related information:
 
 - [Multi-platfom images](../building/multi-platform.md)
 - [containerd image store (Docker Desktop)](../../desktop/containerd.md)
-- [containerd image store (Docker Engine)](../../storage/containerd.md)
+- [containerd image store (Docker Engine)](/engine/storage/containerd.md)
 
 You may also want to consider checking out
 [xx - Dockerfile cross-compilation helpers](https://github.com/tonistiigi/xx).

content/compose/compose-file/05-services.md

@@ -1217,7 +1217,7 @@ There is a performance penalty for applications that swap memory to disk often.
 
 - `none`: Turns off all container networking.
 - `host`: Gives the container raw access to the host's network interface.
-- `service:{name}`: Gives the containers access to the specified service only. For more information, see [Container networks](../../network/_index.md#container-networks).
+- `service:{name}`: Gives the containers access to the specified service only. For more information, see [Container networks](/engine/network/_index.md#container-networks).
 
 ```yml
     network_mode: "host"
@@ -1574,7 +1574,7 @@ web:
   runtime: runc
 ```
 
-The default is `runc`. To use a different runtime, see [Alternative runtimes](../../engine/alternative-runtimes.md).
+The default is `runc`. To use a different runtime, see [Alternative runtimes](/engine/daemon/alternative-runtimes.md).
 
 ### scale
 

content/compose/compose-file/06-networks.md

@@ -73,7 +73,7 @@ networks:
     driver: bridge
 ```
 
-For more information on drivers and available options, see [Network drivers](../../network/drivers/_index.md).
+For more information on drivers and available options, see [Network drivers](/engine/network/drivers/_index.md).
 
 ### driver_opts
 
@@ -103,7 +103,7 @@ networks:
 
 ### enable_ipv6
 
-`enable_ipv6` enables IPv6 networking. For an example, see step four of [Create an IPv6 network](../../config/daemon/ipv6.md).
+`enable_ipv6` enables IPv6 networking. For an example, see step four of [Create an IPv6 network](/engine/daemon/ipv6.md).
 
 ### external
 

content/compose/environment-variables/envvars.md

@@ -6,7 +6,7 @@ aliases:
 - /compose/reference/envvars/
 ---
 
-Compose already comes with pre-defined environment variables. It also inherits common Docker CLI environment variables, such as `DOCKER_HOST` and `DOCKER_CONTEXT`. See [Docker CLI environment variable reference](/engine/reference/commandline/cli/#environment-variables) for details.
+Compose already comes with pre-defined environment variables. It also inherits common Docker CLI environment variables, such as `DOCKER_HOST` and `DOCKER_CONTEXT`. See [Docker CLI environment variable reference](/reference/cli/docker/#environment-variables) for details.
 
 This page contains information on how you can set or change the following pre-defined environment variables if you need to:
 
@@ -187,7 +187,7 @@ For more information, see [Migrate to Compose V2](../migrate.md).
 
 - `COMPOSE_API_VERSION`
     By default the API version is negotiated with the server. Use `DOCKER_API_VERSION`.  
-    See the [Docker CLI environment variable reference](../../../engine/reference/commandline/cli/#environment-variables) page.
+    See the [Docker CLI environment variable reference](/reference/cli/docker/#environment-variables) page.
 - `COMPOSE_HTTP_TIMEOUT`
 - `COMPOSE_TLS_VERSION`
 - `COMPOSE_FORCE_WINDOWS_HOST`

content/compose/gettingstarted.md

@@ -240,7 +240,7 @@ services:
 
 Whenever a file is changed, Compose syncs the file to the corresponding location under `/code` inside the container. Once copied, the bundler updates the running application without a restart.
 
-For more information on how Compose Watch works, see [Use Compose Watch](file-watch.md). Alternatively, see [Manage data in containers](../storage/volumes.md) for other options.
+For more information on how Compose Watch works, see [Use Compose Watch](file-watch.md). Alternatively, see [Manage data in containers](/engine/storage/volumes.md) for other options.
 
 > **Note**
 >

content/compose/gpu-support.md

@@ -4,7 +4,7 @@ keywords: documentation, docs, docker, compose, GPU access, NVIDIA, samples
 title: Turn on GPU access with Docker Compose
 ---
 
-Compose services can define GPU device reservations if the Docker host contains such devices and the Docker Daemon is set accordingly. For this, make sure you install the [prerequisites](../config/containers/resource_constraints.md#gpu) if you haven't already done so.
+Compose services can define GPU device reservations if the Docker host contains such devices and the Docker Daemon is set accordingly. For this, make sure you install the [prerequisites](/engine/containers/resource_constraints.md#gpu) if you haven't already done so.
 
 The examples in the following sections focus specifically on providing service containers access to GPU devices with Docker Compose. 
 You can use either `docker-compose` or `docker compose` commands. For more information, see [Migrate to Compose V2](migrate.md).

content/compose/networking.md

@@ -7,7 +7,7 @@ title: Networking in Compose
 {{< include "compose-eol.md" >}}
 
 By default Compose sets up a single
-[network](../reference/cli/docker/network/create.md) for your app. Each
+[network](/reference/cli/docker/network/create.md) for your app. Each
 container for a service joins the default network and is both reachable by
 other containers on that network, and discoverable by the service's name.
 
@@ -85,13 +85,13 @@ See the [links reference](compose-file/05-services.md#links) for more informatio
 
 ## Multi-host networking
 
-When deploying a Compose application on a Docker Engine with [Swarm mode enabled](../engine/swarm/index.md),
+When deploying a Compose application on a Docker Engine with [Swarm mode enabled](../engine/swarm/_index.md),
 you can make use of the built-in `overlay` driver to enable multi-host communication.
 
 Overlay networks are always created as `attachable`. You can optionally set the [`attachable`](compose-file/06-networks.md#attachable) property to `false`.
 
-Consult the [Swarm mode section](../engine/swarm/index.md), to see how to set up
-a Swarm cluster, and the [Getting started with multi-host networking](../network/network-tutorial-overlay.md)
+Consult the [Swarm mode section](../engine/swarm/_index.md), to see how to set up
+a Swarm cluster, and the [Getting started with multi-host networking](/engine/network/tutorials/overlay.md)
 to learn about multi-host overlay networks.
 
 ## Specify custom networks