refactor: consolidate docker engine content files

Move content files related to Docker Engine to the /engine content
subdirectory, and update links

Signed-off-by: David Karlsson <35727626+dvdksn@users.noreply.github.com>

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/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

content/compose/release-notes.md

@@ -2303,7 +2303,7 @@ naming scheme accordingly before upgrading.
 - Added support for `extra_hosts` in build configuration
 
 - Added support for the [long syntax](compose-file/legacy-versions.md) for volume entries, as previously introduced in the 3.2 format.
-  Using this syntax will create [mounts](../storage/bind-mounts.md) instead of volumes.
+  Using this syntax will create [mounts](/engine/storage/bind-mounts.md) instead of volumes.
 
 #### Compose file version 2.1 and up
 

content/desktop/backup-and-restore.md

@@ -24,7 +24,7 @@ computer, for example.
    Also note that filesystem changes in volume that are attached to the
    container are not included in the image, and must be backed up separately.
 
-   If you used a [named volume](../storage/index.md#more-details-about-mount-types) to store container data, such as databases, refer to the [back up, restore, or migrate data volumes](../storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section.
+   If you used a [named volume](/engine/storage/index.md#more-details-about-mount-types) to store container data, such as databases, refer to the [back up, restore, or migrate data volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section.
 
 2. Use [`docker push`](../reference/cli/docker/image/push.md) to push any
    images you have built locally and want to keep to the [Docker Hub registry](../docker-hub/index.md).
@@ -49,4 +49,4 @@ and [install a different version](release-notes.md) or reset Docker Desktop to f
 2. Re-create your containers if needed, using [`docker run`](../reference/cli/docker/container/run.md),
    or [Docker Compose](../compose/index.md).
 
-Refer to the [backup, restore, or migrate data volumes](../storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section to restore volume data.
+Refer to the [backup, restore, or migrate data volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes) page in the storage section to restore volume data.

content/desktop/install/linux-install.md

@@ -74,7 +74,7 @@ $ sudo systemctl disable docker docker.socket containerd
 
 The Docker CLI can be used to interact with multiple Docker Engines. For example,
 you can use the same Docker CLI to control a local Docker Engine and to control
-a remote Docker Engine instance running in the cloud. [Docker Contexts](../../engine/context/working-with-contexts.md)
+a remote Docker Engine instance running in the cloud. [Docker Contexts](/engine/manage-resources/contexts.md)
 allow you to switch between Docker Engines instances.
 
 When installing Docker Desktop, a dedicated "desktop-linux" context is created to
@@ -112,7 +112,7 @@ desktop-linux
 Current context is now "desktop-linux"
 ```
 
-Refer to the [Docker Context documentation](../../engine/context/working-with-contexts.md) for more details.
+Refer to the [Docker Context documentation](/engine/manage-resources/contexts.md) for more details.
 
 {{< /accordion >}}
 
@@ -241,7 +241,7 @@ Sign out and sign back in so that your group membership is re-evaluated.
 
 - Explore [Docker's core subscriptions](https://www.docker.com/pricing/) to see what Docker can offer you.
 - [Get started with Docker](../../guides/getting-started/_index.md).
-- [Explore Docker Desktop](../use-desktop/index.md) and all its features.
+- [Explore Docker Desktop](../use-desktop/_index.md) and all its features.
 - [Troubleshooting](../troubleshoot/overview.md) describes common problems, workarounds, how to run and submit diagnostics, and submit issues.
 - [FAQs](../faqs/general.md) provide answers to frequently asked questions.
 - [Release notes](../release-notes.md) lists component updates, new features, and improvements associated with Docker Desktop releases.

content/desktop/networking.md

@@ -181,7 +181,7 @@ container to random ports on the host.
 $ docker run -d -P --name webserver nginx
 ```
 
-Alternatively, you can also use [host networking](../network/drivers/host.md#docker-desktop)
+Alternatively, you can also use [host networking](/engine/network/drivers/host.md#docker-desktop)
 to give the container direct access to the network stack of the host.
 
 See the [run command](../reference/cli/docker/container/run.md) for more details on

content/desktop/previous-versions/archive-mac.md

@@ -36,7 +36,7 @@ This page contains release notes for older versions of Docker Desktop for Mac.
   - Re-enable raw as the default disk format for users running macOS 10.13.4 and higher. Note this change only takes effect after a "reset to factory defaults" or "remove all data" (from the Whale menu -> Preferences -> Reset). Related to [docker/for-mac#2625](https://github.com/docker/for-mac/issues/2625)
 
 * Bug fixes and minor changes
-  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
+  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
   - OS X El Captain 10.11 is deprecated in Docker Desktop. You will not be able to install updates after Docker Desktop 18.06.x. We recommend upgrading to the latest version of macOS.
   - Fix bug which would cause VM logs to be written to RAM rather than disk in some cases, and the VM to hang. See [docker/for-mac#2984](https://github.com/docker/for-mac/issues/2984)
   - Fix network connection leak triggered by haproxy TCP health-checks [docker/for-mac#1132](https://github.com/docker/for-mac/issues/1132)

content/desktop/previous-versions/archive-windows.md

@@ -50,7 +50,7 @@ This page contains release notes for older versions of Docker Desktop for Window
   - Kubernetes Support. You can now run a single-node Kubernetes cluster from the "Kubernetes" Pane in Docker for Windows settings and use kubectl commands as well as Docker commands. See [the Kubernetes section](../kubernetes.md)
 
 * Bug fixes and minor changes
-  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset the disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [backup volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
+  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset the disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [backup volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
   - Fix bug which would in some cases cause virtual machine logs to be written to RAM rather than disk, and the virtual machine to hang.
   - Fix security issue with named pipe connection to docker service.
   - Fix VPNKit memory leak. Fixes [docker/for-win#2087](https://github.com/docker/for-win/issues/2087), [moby/vpnkit#371](https://github.com/moby/vpnkit/issues/371)

content/desktop/previous-versions/edge-releases-mac.md

@@ -733,7 +733,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
   - Add an experimental SOCKS server to allow access to container networks, see [docker/for-mac#2670](https://github.com/docker/for-mac/issues/2670#issuecomment-372365274). Also see [docker/for-mac#2721](https://github.com/docker/for-mac/issues/2721)
 
 * Bug fixes and minor changes
-  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
+  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Preferences > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
   - Fix startup issue with AUFS [docker/for-mac#2804](https://github.com/docker/for-mac/issues/2804)
   - Fix status bug which could prevent the Kubernetes cluster from starting. Fixes [docker/for-mac#2990](https://github.com/docker/for-mac/issues/2990)
   - Fix bug which would cause virtual machine logs to be written to RAM rather than disk in some cases, and the virtual machine to hang. See [docker/for-mac#2984](https://github.com/docker/for-mac/issues/2984)

content/desktop/previous-versions/edge-releases-windows.md

@@ -954,7 +954,7 @@ This release contains a Kubernetes upgrade. Note that your local Kubernetes clus
   - New Kubernetes menu item allowing to switch Kubernetes context & connect to clusters other than the local one.
 
 * Bug fixes and minor changes
-  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](../../storage/volumes.md#back-up-restore-or-migrate-data-volumes)
+  - AUFS storage driver is deprecated in Docker Desktop and AUFS support will be removed in the next major release. You can continue with AUFS in Docker Desktop 18.06.x, but you will need to reset disk image (in Settings > Reset menu) before updating to the next major update. You can check documentation to [save images](/reference/cli/docker/image/save/#examples) and [back up volumes](/engine/storage/volumes.md#back-up-restore-or-migrate-data-volumes)
   - Fix startup issue with AUFS
   - Fix status bug which could prevent the kubernetes cluster from starting.
   - Fix bug which would cause VM logs to be written to RAM rather than disk in some cases, and the VM to hang.

content/desktop/release-notes.md

@@ -372,7 +372,7 @@ This can be resolved by adding the user to the **docker-users** group. Before st
 - New [interactive Compose CLI (experimental)](../compose/environment-variables/envvars.md#compose_menu).
 - Beta release of:
   - Air-Gapped Containers with [Settings Management](hardened-desktop/air-gapped-containers/_index.md).
-  - [Host networking](../network/drivers/host.md#docker-desktop) in Docker Desktop.
+  - [Host networking](/engine/network/drivers/host.md#docker-desktop) in Docker Desktop.
   - [Docker Debug](use-desktop/container.md#integrated-terminal) for running containers.
   - [Volumes Backup & Share extension](use-desktop/volumes.md) functionality available in the **Volumes** tab.
 

content/desktop/settings/linux.md

@@ -137,8 +137,8 @@ File share settings are:
 > * Shared folders are designed to allow application code to be edited
 >   on the host while being executed in containers. For non-code items
 >   such as cache directories or databases, the performance will be much
->   better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
->   (named volume) or [data container](../../storage/volumes.md).
+>   better if they are stored in the Linux VM, using a [data volume](/engine/storage/volumes.md)
+>   (named volume) or [data container](/engine/storage/volumes.md).
 { .tip }
 
 ### Proxies
@@ -204,8 +204,8 @@ edit the file using your favorite text editor.
 >
 > Only the **Docker Desktop** daemon uses the configuration file under `$HOME/.docker`.
 > If you manually install Docker Engine alongside Docker Desktop, the manually
-> installed instance uses a `daemon.json` configuration file in a  different location.
-> Refer to [Configure the daemon](../../config/daemon/index.md) for more information
+> installed instance uses a `daemon.json` configuration file in a different location.
+> Refer to [Configure the daemon](/engine/daemon/_index.md) for more information
 > about how to configure the Docker daemon on a manually installed Docker Engine.
 
 To see the full list of possible configuration options, see the

content/desktop/settings/mac.md

@@ -169,8 +169,8 @@ File share settings are:
 > * Shared folders are designed to allow application code to be edited
 >   on the host while being executed in containers. For non-code items
 >   such as cache directories or databases, the performance will be much
->   better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
->   (named volume) or [data container](../../storage/volumes.md).
+>   better if they are stored in the Linux VM, using a [data volume](/engine/storage/volumes.md)
+>   (named volume) or [data container](/engine/storage/volumes.md).
 > * If you share the whole of your home directory into a container, MacOS may
 >   prompt you to give Docker access to personal areas of your home directory such as
 >   your Reminders or Downloads.

content/desktop/settings/windows.md

@@ -163,8 +163,8 @@ File share settings are:
 > * Shared folders are designed to allow application code to be edited
 >   on the host while being executed in containers. For non-code items
 >   such as cache directories or databases, the performance will be much
->   better if they are stored in the Linux VM, using a [data volume](../../storage/volumes.md)
->   (named volume) or [data container](../../storage/volumes.md).
+>   better if they are stored in the Linux VM, using a [data volume](/engine/storage/volumes.md)
+>   (named volume) or [data container](/engine/storage/volumes.md).
 > * Docker Desktop sets permissions to read/write/execute for users, groups and
 >   others [0777 or a+rwx](https://chmodcommand.com/chmod-0777/).
 >   This is not configurable. See [Permissions errors on data directories for shared volumes](../troubleshoot/topics.md).

content/desktop/synchronized-file-sharing.md

@@ -24,7 +24,7 @@ Synchronized file shares is ideal for developers who:
 
 A Synchronized file share behaves just like a virtual file share, but takes advantage of a high-performance, low-latency code synchronization engine to create a synchronized cache of the host files on an ext4 filesystem within the Docker Desktop VM. If you make filesystem changes on the host or in the VM’s containers, it propagates via bidirectional synchronization.
 
-After creating a file share instance, any container using a bind mount that points to a location on the host filesystem matching the specified synchronized file share location, or a subdirectory within it,  utilizes the Synchronized File Shares feature. Bind mounts that don't satisfy this condition are passed to the normal virtual filesystem [bind-mounting mechanism](../storage/bind-mounts.md), for example VirtioFS or gRPC-FUSE.
+After creating a file share instance, any container using a bind mount that points to a location on the host filesystem matching the specified synchronized file share location, or a subdirectory within it,  utilizes the Synchronized File Shares feature. Bind mounts that don't satisfy this condition are passed to the normal virtual filesystem [bind-mounting mechanism](/engine/storage/bind-mounts.md), for example VirtioFS or gRPC-FUSE.
 
 > **Note**
 >

content/desktop/troubleshoot/overview.md

@@ -306,7 +306,7 @@ Desktop at `$HOME/.docker/desktop/log/`.
 
 ## View the Docker daemon logs
 
-Refer to the [Read the daemon logs](../../config/daemon/logs.md) section
+Refer to the [Read the daemon logs](/engine/daemon/logs.md) section
 to learn how to view the Docker Daemon logs.
 
 ## Further resources

content/desktop/use-desktop/volumes.md

@@ -5,7 +5,7 @@ title: Explore Volumes
 ---
 
 The **Volumes** view in Docker Dashboard lets you create, delete, and perform
-other actions on your [volumes](../../storage/volumes.md). You can also see
+other actions on your [volumes](/engine/storage/volumes.md). You can also see
 which volumes are being used as well as inspect the files and folders in your
 volumes.
 
@@ -34,7 +34,7 @@ doing the following:
 ## Create a volume
 
 You use the following steps to create an empty volume. Alternatively, if you
-[start a container with a volume](../../storage/volumes.md#start-a-container-with-a-volume)
+[start a container with a volume](/engine/storage/volumes.md#start-a-container-with-a-volume)
 that doesn't yet exist, Docker creates the volume for you.
 
 To create a volume:
@@ -43,7 +43,7 @@ To create a volume:
 2. In the **New Volume** modal, specify a volume name, and then select
    **Create**.
 
-To use the volume with a container, see [Use volumes](../../storage/volumes.md#start-a-container-with-a-volume).
+To use the volume with a container, see [Use volumes](/engine/storage/volumes.md#start-a-container-with-a-volume).
 
 ## Inspect a volume
 
@@ -246,4 +246,4 @@ To import a volume:
 ## Additional resources
 
 - [Persisting container data](../../guides/docker-concepts/running-containers/persisting-container-data.md)
-- [Use volumes](../../storage/volumes.md)
+- [Use volumes](/engine/storage/volumes.md)

content/engine/cli/completion.md

@@ -2,6 +2,8 @@
 title: CLI completion
 description: Set up your shell to get autocomplete for Docker commands and flags
 keywords: cli, shell, fish, bash, zsh, completion, options
+aliases:
+  - /config/completion/
 ---
 
 You can generate a shell completion script for the Docker CLI using the `docker

content/engine/cli/filter.md

@@ -4,6 +4,8 @@ description: |
   Use the filtering function in the CLI to selectively include resources
   that match the pattern you define.
 keywords: cli, filter, commands, output, include, exclude
+aliases:
+  - /config/filter/
 ---
 
 You can use the `--filter` flag to scope your commands. When filtering, the
@@ -70,7 +72,7 @@ busybox      glibc     7338d0c72c65   2 hours ago   6.09MB
 
 ### Multiple negated filters
 
-Some commands support negated filters on [labels](./labels-custom-metadata.md).
+Some commands support negated filters on [labels](/engine/manage-resources/labels.md).
 Negated filters only consider results that don't match the specified patterns.
 The following command prunes all containers that aren't labeled `foo`.
 
@@ -92,21 +94,21 @@ $ docker container prune --filter "label!=foo" --filter "label!=bar"
 For more information about filtering commands, refer to the CLI reference
 description for commands that support the `--filter` flag:
 
-- [`docker config ls`](../reference/cli/docker/config/ls.md)
-- [`docker container prune`](../reference/cli/docker/container/prune.md)
-- [`docker image prune`](../reference/cli/docker/image/prune.md)
-- [`docker image ls`](../reference/cli/docker/image/ls.md)
-- [`docker network ls`](../reference/cli/docker/network/ls.md)
-- [`docker network prune`](../reference/cli/docker/network/prune.md)
-- [`docker node ls`](../reference/cli/docker/node/ls.md)
-- [`docker node ps`](../reference/cli/docker/node/ps.md)
-- [`docker plugin ls`](../reference/cli/docker/plugin/ls.md)
-- [`docker container ls`](../reference/cli/docker/container/ls.md)
-- [`docker search`](../reference/cli/docker/search.md)
-- [`docker secret ls`](../reference/cli/docker/secret/ls.md)
-- [`docker service ls`](../reference/cli/docker/service/ls.md)
-- [`docker service ps`](../reference/cli/docker/service/ps.md)
-- [`docker stack ps`](../reference/cli/docker/stack/ps.md)
-- [`docker system prune`](../reference/cli/docker/system/prune.md)
-- [`docker volume ls`](../reference/cli/docker/volume/ls.md)
-- [`docker volume prune`](../reference/cli/docker/volume/prune.md)
+- [`docker config ls`](/reference/cli/docker/config/ls.md)
+- [`docker container prune`](/reference/cli/docker/container/prune.md)
+- [`docker image prune`](/reference/cli/docker/image/prune.md)
+- [`docker image ls`](/reference/cli/docker/image/ls.md)
+- [`docker network ls`](/reference/cli/docker/network/ls.md)
+- [`docker network prune`](/reference/cli/docker/network/prune.md)
+- [`docker node ls`](/reference/cli/docker/node/ls.md)
+- [`docker node ps`](/reference/cli/docker/node/ps.md)
+- [`docker plugin ls`](/reference/cli/docker/plugin/ls.md)
+- [`docker container ls`](/reference/cli/docker/container/ls.md)
+- [`docker search`](/reference/cli/docker/search.md)
+- [`docker secret ls`](/reference/cli/docker/secret/ls.md)
+- [`docker service ls`](/reference/cli/docker/service/ls.md)
+- [`docker service ps`](/reference/cli/docker/service/ps.md)
+- [`docker stack ps`](/reference/cli/docker/stack/ps.md)
+- [`docker system prune`](/reference/cli/docker/system/prune.md)
+- [`docker volume ls`](/reference/cli/docker/volume/ls.md)
+- [`docker volume prune`](/reference/cli/docker/volume/prune.md)

content/engine/cli/formatting.md

@@ -4,6 +4,7 @@ keywords: format, formatting, output, templates, log
 title: Format command and log output
 aliases:
   - /engine/admin/formatting/
+  - /config/formatting/
 ---
 
 Docker supports [Go templates](https://golang.org/pkg/text/template/) which you

content/engine/cli/otel.md

@@ -2,6 +2,8 @@
 title: OpenTelemetry for the Docker CLI
 description: Learn about how to capture OpenTelemetry metrics for the Docker command line
 keywords: otel, opentelemetry, telemetry, traces, tracing, metrics, logs
+aliases:
+  - /config/otel/
 ---
 
 {{< introduced engine 26.1.0 >}}

content/engine/cli/proxy.md

@@ -1,7 +1,9 @@
 ---
-title: Configure Docker to use a proxy server
-description: How to configure the Docker client to use a proxy server
+title: Use a proxy server with the Docker CLI
+description: How to configure the Docker client CLI to use a proxy server
 keywords: network, networking, proxy, client
+aliases:
+  - /network/proxy/
 ---
 
 This page describes how to configure the Docker CLI to use proxies via
@@ -9,12 +11,12 @@ environment variables in containers.
 
 This page doesn't describe how to configure proxies for the Docker daemon.
 For instructions on configuring Docker Desktop to use HTTP/HTTPS proxies, see
-[proxies on Mac](../desktop/settings/mac.md#proxies),
-[proxies on Windows](../desktop/settings/windows.md#proxies), and
-[proxies on Linux](../desktop/settings/linux.md#proxies).
+[proxies on Mac](/desktop/settings/mac.md#proxies),
+[proxies on Windows](/desktop/settings/windows.md#proxies), and
+[proxies on Linux](/desktop/settings/linux.md#proxies).
 
 If you're running Docker Engine without Docker Desktop, refer to
-[Configure the Docker daemon to use a proxy](../config/daemon/proxy.md)
+[Configure the Docker daemon to use a proxy](/engine/daemon/proxy.md)
 to learn how to configure a proxy server for the Docker daemon (`dockerd`) itself.
 
 If your container needs to use an HTTP, HTTPS, or FTP proxy server, you can
@@ -79,7 +81,7 @@ These settings are used to configure proxy environment variables for containers
 only, and not used as proxy settings for the Docker CLI or the Docker Engine
 itself.
 Refer to the [environment variables](/reference/cli/docker/#environment-variables)
-and [configure the Docker daemon to use a proxy server](../config/daemon/proxy.md#httphttps-proxy)
+and [configure the Docker daemon to use a proxy server](/engine/daemon/proxy.md#httphttps-proxy)
 sections for configuring proxy settings for the CLI and daemon.
 
 ### Run containers with a proxy configuration
@@ -174,7 +176,7 @@ $ docker run --env HTTP_PROXY="http://proxy.example.com:3128" redis
 
 For a list of all the proxy-related build arguments that you can use with the
 `docker build` command, see
-[Predefined ARGs](../reference/dockerfile.md#predefined-args).
+[Predefined ARGs](/reference/dockerfile.md#predefined-args).
 These proxy values are only available in the build container.
 They're not included in the build output.
 

content/engine/containers/live-restore.md

@@ -4,6 +4,7 @@ keywords: docker, upgrade, daemon, dockerd, live-restore, daemonless container
 title: Live restore
 aliases:
   - /engine/admin/live-restore/
+  - /config/containers/live-restore/
 ---
 
 By default, when the Docker daemon terminates, it shuts down running containers.

content/engine/containers/multi-service_container.md

@@ -7,6 +7,7 @@ aliases:
   - /engine/admin/multi-service_container/
   - /engine/admin/using_supervisord/
   - /engine/articles/using_supervisord/
+  - /config/containers/multi-service_container/
 ---
 
 A container's main running process is the `ENTRYPOINT` and/or `CMD` at the

content/engine/containers/resource_constraints.md

@@ -4,6 +4,7 @@ description: Specify the runtime options for a container
 keywords: docker, daemon, configuration, runtime
 aliases:
   - /engine/admin/resource_constraints/
+  - /config/containers/resource_constraints/
 ---
 
 By default, a container has no resource constraints and can use as much of a

content/engine/containers/runmetrics.md

@@ -7,6 +7,7 @@ aliases:
   - /engine/articles/run_metrics/
   - /engine/articles/runmetrics/
   - /engine/admin/runmetrics/
+  - /config/containers/runmetrics/
 ---
 
 ## Docker stats

content/engine/containers/start-containers-automatically.md

@@ -6,9 +6,10 @@ aliases:
   - /engine/articles/host_integration/
   - /engine/admin/host_integration/
   - /engine/admin/start-containers-automatically/
+  - /config/containers/start-containers-automatically/
 ---
 
-Docker provides [restart policies](../../engine/reference/run.md#restart-policies---restart)
+Docker provides [restart policies](/engine/containers/run.md#restart-policies---restart)
 to control whether your containers start automatically when they exit, or when
 Docker restarts. Restart policies start linked containers in the correct order.
 Docker recommends that you use restart policies, and avoid using process
@@ -66,7 +67,7 @@ Keep the following in mind when using restart policies:
 
 - Restart policies only apply to containers. To configure restart policies for
   Swarm services, see
-  [flags related to service restart](../../reference/cli/docker/service/create.md).
+  [flags related to service restart](/reference/cli/docker/service/create.md).
 
 ### Restarting foreground containers
 

content/engine/daemon/_index.md

@@ -23,6 +23,7 @@ aliases:
   - /engine/articles/dsc/
   - /engine/articles/puppet/
   - /engine/userguide/
+  - /config/daemon/
 ---
 
 This page shows you how to customize the Docker daemon, `dockerd`.
@@ -67,7 +68,7 @@ You can also explicitly specify the location of the configuration file on
 startup, using the `dockerd --config-file` flag.
 
 Learn about the available configuration options in the
-[dockerd reference docs](../../reference/cli/dockerd.md#daemon-configuration-file)
+[dockerd reference docs](/reference/cli/dockerd.md#daemon-configuration-file)
 
 ### Configuration using flags
 
@@ -86,7 +87,7 @@ $ dockerd --debug \
 ```
 
 Learn about the available configuration options in the
-[dockerd reference docs](../../reference/cli/dockerd.md), or by
+[dockerd reference docs](/reference/cli/dockerd.md), or by
 running:
 
 ```console
@@ -123,8 +124,8 @@ to troubleshoot.
 Many specific configuration options are discussed throughout the Docker
 documentation. Some places to go next include:
 
-- [Automatically start containers](../containers/start-containers-automatically.md)
-- [Limit a container's resources](../containers/resource_constraints.md)
-- [Configure storage drivers](../../storage/storagedriver/select-storage-driver.md)
-- [Container security](../../engine/security/_index.md)
+- [Automatically start containers](/engine/containers/start-containers-automatically.md)
+- [Limit a container's resources](/engine/containers/resource_constraints.md)
+- [Configure storage drivers](/engine/storage/drivers/select-storage-driver.md)
+- [Container security](/engine/security/_index.md)
 - [Configure the Docker daemon to use a proxy](./proxy.md)

content/engine/daemon/alternative-runtimes.md

@@ -1,13 +1,12 @@
 ---
 title: Alternative container runtimes
-description: 'Docker Engine uses runc as the default container runtime, but you
-
+description: |
+  Docker Engine uses runc as the default container runtime, but you
   can specify alternative runtimes using the CLI or by configuring
-
   the daemon
-
-  '
 keywords: engine, runtime, containerd, runtime v2, shim
+aliases:
+  - /engine/alternative-runtimes/
 ---
 
 Docker Engine uses containerd for managing the container lifecycle,
@@ -107,7 +106,7 @@ use the `runtimes` option in the daemon configuration file.
    ```
 
 For more information about the configuration options for containerd shims, see
-[Configure containerd shims](./../reference/cli/dockerd.md#configure-containerd-shims).
+[Configure containerd shims](/reference/cli/dockerd.md#configure-containerd-shims).
 
 ## Examples
 
@@ -127,7 +126,7 @@ youki functions as a drop-in replacement for runc, meaning it relies on the
 runc shim to invoke the runtime binary. When you register runtimes acting as
 runc replacements, you configure the path to the runtime executable, and
 optionally a set of runtime arguments. For more information, see
-[Configure runc drop-in replacements](./../reference/cli/dockerd.md#configure-runc-drop-in-replacements).
+[Configure runc drop-in replacements](/reference/cli/dockerd.md#configure-runc-drop-in-replacements).
 
 To add youki as a container runtime:
 
@@ -176,7 +175,7 @@ plus the added sandboxing provided by the Wasm runtime environment.
 
 To add Wasmtime as a container runtime, follow these steps:
 
-1. Turn on the [containerd image store](../storage/containerd.md)
+1. Turn on the [containerd image store](/engine/storage/containerd.md)
    feature in the daemon configuration file.
 
    > **Note**
@@ -233,6 +232,6 @@ $ docker run --rm \
 ## Related information
 
 - To learn more about the configuration options for container runtimes,
-  see [Configure container runtimes](./../reference/cli/dockerd.md#configure-container-runtimes).
+  see [Configure container runtimes](/reference/cli/dockerd.md#configure-container-runtimes).
 - You can configure which runtime that the daemon should use as its default.
-  Refer to [Configure the default container runtime](./../reference/cli/dockerd.md#configure-the-default-container-runtime).
+  Refer to [Configure the default container runtime](/reference/cli/dockerd.md#configure-the-default-container-runtime).

content/engine/daemon/ipv6.md

@@ -4,6 +4,7 @@ description: How to enable IPv6 support in the Docker daemon
 keywords: daemon, network, networking, ipv6
 aliases:
 - /engine/userguide/networking/default_network/ipv6/
+- /config/daemon/ipv6/
 ---
 
 IPv6 is only supported on Docker daemons running on Linux hosts.
@@ -191,4 +192,4 @@ Engine.
 
 ## Next steps
 
-- [Networking overview](../../network/index.md)
+- [Networking overview](/engine/network/_index.md)

content/engine/daemon/logs.md

@@ -2,6 +2,8 @@
 title: Read the daemon logs
 description: How to read the event logs for the Docker daemon
 keywords: docker, daemon, configuration, troubleshooting, logging
+aliases:
+  - /config/daemon/logs/
 ---
 
 The daemon logs may help you diagnose problems. The logs may be saved in one of

content/engine/daemon/prometheus.md

@@ -6,6 +6,7 @@ aliases:
   - /engine/admin/prometheus/
   - /config/thirdparty/monitoring/
   - /config/thirdparty/prometheus/
+  - /config/daemon/prometheus/
 ---
 
 [Prometheus](https://prometheus.io/) is an open-source systems monitoring and

content/engine/daemon/proxy.md

@@ -8,6 +8,7 @@ aliases:
   - /engine/admin/systemd/
   - /engine/articles/systemd/
   - /config/daemon/systemd/
+  - /config/daemon/proxy/
 ---
 
 <a name="httphttps-proxy"><!-- included for deep-links to old section --></a>
@@ -19,7 +20,7 @@ and to reach other nodes in a Docker swarm.
 
 This page describes how to configure a proxy for the Docker daemon. For
 instructions on configuring proxy settings for the Docker CLI, see [Configure
-Docker to use a proxy server](../../network/proxy.md).
+Docker CLI to use a proxy server](/engine/cli/proxy.md).
 
 There are two ways you can configure these settings:
 

content/engine/daemon/remote-access.md

@@ -5,6 +5,8 @@ description:
   socket
 keywords: configuration, daemon, remote access, engine
 title: Configure remote access for Docker daemon
+aliases:
+  - /config/daemon/remote-access/
 ---
 
 By default, the Docker daemon listens for connections on a Unix socket to accept

content/engine/daemon/start.md

@@ -2,6 +2,8 @@
 title: Start the daemon
 description: Starting the Docker daemon manually
 keywords: docker, daemon, configuration, troubleshooting
+aliases:
+  - /config/daemon/start/
 ---
 
 This page shows how to start the daemon, either manually or using OS utilities.
@@ -45,4 +47,4 @@ INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
 ```
 
 To stop Docker when you have started it manually, issue a `Ctrl+C` in your
-terminal.
+terminal.

content/engine/daemon/troubleshoot.md

@@ -8,6 +8,7 @@ keywords: |
 aliases:
   - /engine/install/troubleshoot/
   - /storage/troubleshooting_volume_errors/
+  - /config/daemon/troubleshooting/
 tags: [Troubleshooting]
 ---
 

content/engine/faq.md

@@ -101,14 +101,14 @@ thousands or even millions of containers.
 ### How do I connect Docker containers?
 
 Currently the recommended way to connect containers is via the Docker network
-feature. You can see details of [how to work with Docker networks](../network/drivers/bridge.md).
+feature. You can see details of [how to work with Docker networks](/engine/network/drivers/bridge.md).
 
 ### How do I run more than one process in a Docker container?
 
 This approach is discouraged for most use cases. For maximum efficiency and
 isolation, each container should address one specific area of concern. However,
 if you need to run multiple services within a single container, see
-[Run multiple services in a container](../config/containers/multi-service_container.md).
+[Run multiple services in a container](/engine/containers/multi-service_container.md).
 
 ### How do I report a security issue with Docker?
 

content/engine/install/debian.md

@@ -29,12 +29,12 @@ To get started with Docker Engine on Debian, make sure you
 - If you use ufw or firewalld to manage firewall settings, be aware that
   when you expose container ports using Docker, these ports bypass your
   firewall rules. For more information, refer to
-  [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
+  [Docker and ufw](/engine/network/packet-filtering-firewalls.md#docker-and-ufw).
 - Docker is only compatible with `iptables-nft` and `iptables-legacy`.
   Firewall rules created with `nft` are not supported on a system with Docker installed.
   Make sure that any firewall rulesets you use are created with `iptables` or `ip6tables`,
   and that you add them to the `DOCKER-USER` chain,
-  see [Packet filtering and firewalls](../../network/packet-filtering-firewalls.md).
+  see [Packet filtering and firewalls](/engine/network/packet-filtering-firewalls.md).
 
 ### OS requirements
 

content/engine/install/linux-postinstall.md

@@ -117,11 +117,11 @@ $ sudo systemctl disable containerd.service
 You can use systemd unit files to configure the Docker service on startup,
 for example to add an HTTP proxy, set a different directory or partition for the
 Docker runtime files, or other customizations. For an example, see
-[Configure the daemon to use a proxy](../../config/daemon/proxy.md#systemd-unit-file).
+[Configure the daemon to use a proxy](/engine/daemon/proxy.md#systemd-unit-file).
 
 ## Configure default logging driver
 
-Docker provides [logging drivers](../../config/containers/logging/index.md) for
+Docker provides [logging drivers](/engine/logging/_index.md) for
 collecting and viewing log data from all containers running on a host. The
 default logging driver, `json-file`, writes log data to JSON-formatted files on
 the host filesystem. Over time, these log files expand in size, leading to
@@ -131,13 +131,13 @@ To avoid issues with overusing disk for log data, consider one of the following
 options:
 
 - Configure the `json-file` logging driver to turn on
-  [log rotation](../../config/containers/logging/json-file.md).
+  [log rotation](/engine/logging/drivers/json-file.md).
 - Use an
-  [alternative logging driver](../../config/containers/logging/configure.md#configure-the-default-logging-driver)
-  such as the ["local" logging driver](../../config/containers/logging/local.md)
+  [alternative logging driver](/engine/logging/configure.md#configure-the-default-logging-driver)
+  such as the ["local" logging driver](/engine/logging/drivers/local.md)
   that performs log rotation by default.
 - Use a logging driver that sends logs to a remote logging aggregator.
 
 ## Next steps
 
-- Take a look at the [Docker workshop](../../guides/workshop/_index.md) to learn how to build an image and run it as a containerized application.
+- Take a look at the [Docker workshop](/guides/workshop/_index.md) to learn how to build an image and run it as a containerized application.

content/engine/install/raspberry-pi-os.md

@@ -35,12 +35,12 @@ To get started with Docker Engine on Raspberry Pi OS, make sure you
 - If you use ufw or firewalld to manage firewall settings, be aware that
   when you expose container ports using Docker, these ports bypass your
   firewall rules. For more information, refer to
-  [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
+  [Docker and ufw](/engine/network/packet-filtering-firewalls.md#docker-and-ufw).
 - Docker is only compatible with `iptables-nft` and `iptables-legacy`.
   Firewall rules created with `nft` are not supported on a system with Docker installed.
   Make sure that any firewall rulesets you use are created with `iptables` or `ip6tables`,
   and that you add them to the `DOCKER-USER` chain,
-  see [Packet filtering and firewalls](../../network/packet-filtering-firewalls.md).
+  see [Packet filtering and firewalls](/engine/network/packet-filtering-firewalls.md).
 
 ### OS requirements
 

content/engine/install/ubuntu.md

@@ -37,12 +37,12 @@ To get started with Docker Engine on Ubuntu, make sure you
 - If you use ufw or firewalld to manage firewall settings, be aware that
   when you expose container ports using Docker, these ports bypass your
   firewall rules. For more information, refer to
-  [Docker and ufw](../../network/packet-filtering-firewalls.md#docker-and-ufw).
+  [Docker and ufw](/engine/network/packet-filtering-firewalls.md#docker-and-ufw).
 - Docker is only compatible with `iptables-nft` and `iptables-legacy`.
   Firewall rules created with `nft` are not supported on a system with Docker installed.
   Make sure that any firewall rulesets you use are created with `iptables` or `ip6tables`,
   and that you add them to the `DOCKER-USER` chain,
-  see [Packet filtering and firewalls](../../network/packet-filtering-firewalls.md).
+  see [Packet filtering and firewalls](/engine/network/packet-filtering-firewalls.md).
 
 ### OS requirements
 

content/engine/logging/_index.md

@@ -5,6 +5,7 @@ title: View container logs
 aliases:
   - /engine/admin/logging/
   - /engine/admin/logging/view_container_logs/
+  - /config/containers/logging/
 ---
 
 The `docker logs` command shows information logged by a running container. The

content/engine/logging/configure.md

@@ -9,22 +9,23 @@ aliases:
   - /engine/admin/reference/logging/
   - /engine/admin/logging/logentries/
   - /engine/admin/logging/overview/
+  - /engine/admin/logging/
 ---
 
-Docker includes multiple logging mechanisms to help you
-[get information from running containers and services](index.md).
-These mechanisms are called logging drivers. Each Docker daemon has a default
-logging driver, which each container uses unless you configure it to use a
-different logging driver, or log driver for short.
+Docker includes multiple logging mechanisms to help you get information from
+running containers and services. These mechanisms are called logging drivers.
+Each Docker daemon has a default logging driver, which each container uses
+unless you configure it to use a different logging driver, or log driver for
+short.
 
-As a default, Docker uses the [`json-file` logging driver](json-file.md), which
+As a default, Docker uses the [`json-file` logging driver](drivers/json-file.md), which
 caches container logs as JSON internally. In addition to using the logging drivers
 included with Docker, you can also implement and use [logging driver plugins](plugins.md).
 
 > **Tip: use the `local` logging driver to prevent disk-exhaustion**
 >
 > By default, no log-rotation is performed. As a result, log-files stored by the
-> default [`json-file` logging driver](json-file.md) logging driver can cause
+> default [`json-file` logging driver](drivers/json-file.md) logging driver can cause
 > a significant amount of disk space to be used for containers that generate much
 > output, which can lead to disk space exhaustion.
 >
@@ -36,7 +37,7 @@ included with Docker, you can also implement and use [logging driver plugins](pl
 > log-rotation by default, and uses a more efficient file format. Refer to the
 > [Configure the default logging driver](#configure-the-default-logging-driver)
 > section below to learn how to configure the `local` logging driver as a default,
-> and the [local file logging driver](local.md) page for more details about the
+> and the [local file logging driver](drivers/local.md) page for more details about the
 > `local` logging driver.
 { .tip }
 
@@ -49,7 +50,7 @@ configuration file. Refer to the "daemon configuration file" section in the
 for details.
 
 The default logging driver is `json-file`. The following example sets the default
-logging driver to the [`local` log driver](local.md):
+logging driver to the [`local` log driver](drivers/local.md):
 
 ```json
 {
@@ -185,19 +186,19 @@ documentation for its configurable options, if applicable. If you are using
 [logging driver plugins](plugins.md), you may
 see more options.
 
-| Driver                        | Description                                                                                                 |
-| :---------------------------- | :---------------------------------------------------------------------------------------------------------- |
-| `none`                        | No logs are available for the container and `docker logs` does not return any output.                       |
-| [`local`](local.md)           | Logs are stored in a custom format designed for minimal overhead.                                           |
-| [`json-file`](json-file.md)   | The logs are formatted as JSON. The default logging driver for Docker.                                      |
-| [`syslog`](syslog.md)         | Writes logging messages to the `syslog` facility. The `syslog` daemon must be running on the host machine.  |
-| [`journald`](journald.md)     | Writes log messages to `journald`. The `journald` daemon must be running on the host machine.               |
-| [`gelf`](gelf.md)             | Writes log messages to a Graylog Extended Log Format (GELF) endpoint such as Graylog or Logstash.           |
-| [`fluentd`](fluentd.md)       | Writes log messages to `fluentd` (forward input). The `fluentd` daemon must be running on the host machine. |
-| [`awslogs`](awslogs.md)       | Writes log messages to Amazon CloudWatch Logs.                                                              |
-| [`splunk`](splunk.md)         | Writes log messages to `splunk` using the HTTP Event Collector.                                             |
-| [`etwlogs`](etwlogs.md)       | Writes log messages as Event Tracing for Windows (ETW) events. Only available on Windows platforms.         |
-| [`gcplogs`](gcplogs.md)       | Writes log messages to Google Cloud Platform (GCP) Logging.                                                 |
+| Driver                                | Description                                                                                                 |
+| :------------------------------------ | :---------------------------------------------------------------------------------------------------------- |
+| `none`                                | No logs are available for the container and `docker logs` does not return any output.                       |
+| [`local`](drivers/local.md)           | Logs are stored in a custom format designed for minimal overhead.                                           |
+| [`json-file`](drivers/json-file.md)   | The logs are formatted as JSON. The default logging driver for Docker.                                      |
+| [`syslog`](drivers/syslog.md)         | Writes logging messages to the `syslog` facility. The `syslog` daemon must be running on the host machine.  |
+| [`journald`](drivers/journald.md)     | Writes log messages to `journald`. The `journald` daemon must be running on the host machine.               |
+| [`gelf`](drivers/gelf.md)             | Writes log messages to a Graylog Extended Log Format (GELF) endpoint such as Graylog or Logstash.           |
+| [`fluentd`](drivers/fluentd.md)       | Writes log messages to `fluentd` (forward input). The `fluentd` daemon must be running on the host machine. |
+| [`awslogs`](drivers/awslogs.md)       | Writes log messages to Amazon CloudWatch Logs.                                                              |
+| [`splunk`](drivers/splunk.md)         | Writes log messages to `splunk` using the HTTP Event Collector.                                             |
+| [`etwlogs`](drivers/etwlogs.md)       | Writes log messages as Event Tracing for Windows (ETW) events. Only available on Windows platforms.         |
+| [`gcplogs`](drivers/gcplogs.md)       | Writes log messages to Google Cloud Platform (GCP) Logging.                                                 |
 
 ## Limitations of logging drivers
 

content/engine/logging/drivers/awslogs.md

@@ -5,6 +5,7 @@ title: Amazon CloudWatch Logs logging driver
 aliases:
   - /engine/reference/logging/awslogs/
   - /engine/admin/logging/awslogs/
+  - /config/containers/logging/awslogs/
 ---
 
 The `awslogs` logging driver sends container logs to

content/engine/logging/drivers/etwlogs.md

@@ -4,6 +4,7 @@ keywords: ETW, docker, logging, driver
 title: ETW logging driver
 aliases:
   - /engine/admin/logging/etwlogs/
+  - /config/containers/logging/etwlogs/
 ---
 
 The Event Tracing for Windows (ETW) logging driver forwards container logs as ETW events.

content/engine/logging/drivers/fluentd.md

@@ -6,6 +6,7 @@ aliases:
   - /engine/reference/logging/fluentd/
   - /reference/logging/fluentd/
   - /engine/admin/logging/fluentd/
+  - /config/containers/logging/fluentd/
 ---
 
 The `fluentd` logging driver sends container logs to the

content/engine/logging/drivers/gcplogs.md

@@ -4,6 +4,7 @@ keywords: gcplogs, google, docker, logging, driver
 title: Google Cloud Logging driver
 aliases:
   - /engine/admin/logging/gcplogs/
+  - /config/containers/logging/gcplogs/
 ---
 
 The Google Cloud Logging driver sends container logs to

content/engine/logging/drivers/gelf.md

@@ -5,6 +5,7 @@ title: Graylog Extended Format logging driver
 aliases:
   - /engine/reference/logging/gelf/
   - /engine/admin/logging/gelf/
+  - /config/containers/logging/gelf/
 ---
 
 The `gelf` logging driver is a convenient format that's understood by a number of tools such as

content/engine/logging/drivers/journald.md

@@ -5,6 +5,7 @@ title: Journald logging driver
 aliases:
   - /engine/reference/logging/journald/
   - /engine/admin/logging/journald/
+  - /config/containers/logging/journald/
 ---
 
 The `journald` logging driver sends container logs to the

content/engine/logging/drivers/json-file.md

@@ -5,6 +5,7 @@ title: JSON File logging driver
 aliases:
   - /engine/reference/logging/json-file/
   - /engine/admin/logging/json-file/
+  - /config/containers/logging/json-file/
 ---
 
 By default, Docker captures the standard output (and standard error) of all your containers,

content/engine/logging/drivers/local.md

@@ -5,6 +5,7 @@ title: Local file logging driver
 aliases:
   - /engine/reference/logging/local/
   - /engine/admin/logging/local/
+  - /config/containers/logging/local/
 ---
 
 The `local` logging driver captures output from container's stdout/stderr and

content/engine/logging/drivers/splunk.md

@@ -5,6 +5,7 @@ title: Splunk logging driver
 aliases:
   - /engine/reference/logging/splunk/
   - /engine/admin/logging/splunk/
+  - /config/containers/logging/splunk/
 ---
 
 The `splunk` logging driver sends container logs to

content/engine/logging/drivers/syslog.md

@@ -5,6 +5,7 @@ title: Syslog logging driver
 aliases:
   - /engine/reference/logging/syslog/
   - /engine/admin/logging/syslog/
+  - /config/containers/logging/syslog/
 ---
 
 The `syslog` logging driver routes logs to a `syslog` server. The `syslog` protocol uses

content/engine/logging/dual-logging.md

@@ -6,12 +6,14 @@ keywords: >
   docker, logging, driver, dual logging, dual logging, cache, ring-buffer,
   configuration
 title: Use docker logs with remote logging drivers
+aliases:
+  - /config/containers/logging/dual-logging/
 ---
 
 ## Overview
 
 You can use the `docker logs` command to read container logs regardless of the
-configured logging driver or plugin. Docker Engine uses the [`local`](local.md)
+configured logging driver or plugin. Docker Engine uses the [`local`](drivers/local.md)
 logging driver to act as cache for reading the latest logs of your containers.
 This is called dual logging. By default, the cache has log-file rotation
 enabled, and is limited to a maximum of 5 files of 20 MB each (before
@@ -109,7 +111,7 @@ as a default, with dual logging caching enabled:
 ### Configuration options
 
 The dual logging cache accepts the same configuration options as the
-[`local` logging driver](local.md), but with a `cache-` prefix. These options
+[`local` logging driver](drivers/local.md), but with a `cache-` prefix. These options
 can be specified per container, and defaults for new containers can be set using
 the [daemon configuration file](/reference/cli/dockerd/#daemon-configuration-file).
 
@@ -134,7 +136,7 @@ through a remote logging system, and if there is no need to read logs through
 Caching can be disabled for individual containers or by default for new containers,
 when using the [daemon configuration file](/reference/cli/dockerd/#daemon-configuration-file).
 
-The following example uses the daemon configuration file to use the [`splunk`](splunk.md)
+The following example uses the daemon configuration file to use the [`splunk`](drivers/splunk.md)
 logging driver as a default, with caching disabled:
 
 ```console

content/engine/logging/log_tags.md

@@ -5,6 +5,7 @@ title: Customize log driver output
 aliases:
   - /engine/reference/logging/log_tags/
   - /engine/admin/logging/log_tags/
+  - /config/containers/logging/log_tags/
 ---
 
 The `tag` log option specifies how to format a tag that identifies the

content/engine/logging/plugins.md

@@ -4,6 +4,7 @@ title: Use a logging driver plugin
 keywords: logging, driver, plugins, monitoring
 aliases:
   - /engine/admin/logging/plugins/
+  - /engine/reference/logging/plugins/
 ---
 
 Docker logging plugins allow you to extend and customize Docker's logging

content/engine/manage-resources/contexts.md

@@ -2,6 +2,8 @@
 title: Docker contexts
 description: Learn about managing multiple daemons from a single client with contexts
 keywords: engine, context, cli, daemons, remote
+aliases:
+  - /engine/context/working-with-contexts/
 ---
 
 ## Introduction

content/engine/manage-resources/labels.md

@@ -4,6 +4,7 @@ keywords: labels, metadata, docker, annotations
 title: Docker object labels
 aliases:
   - /engine/userguide/labels-custom-metadata/
+  - /config/labels-custom-metadata/
 ---
 
 Labels are a mechanism for applying metadata to Docker objects, including:
@@ -79,37 +80,37 @@ Labels on Swarm nodes and services can be updated dynamically.
 
 - Images and containers
 
-  - [Adding labels to images](../reference/dockerfile.md#label)
-  - [Overriding a container's labels at runtime](../reference/cli/docker/container/run.md#label)
-  - [Inspecting labels on images or containers](../reference/cli/docker/inspect.md)
-  - [Filtering images by label](../reference/cli/docker/image/ls.md#filter)
-  - [Filtering containers by label](../reference/cli/docker/container/ls.md#filter)
+  - [Adding labels to images](/reference/dockerfile.md#label)
+  - [Overriding a container's labels at runtime](/reference/cli/docker/container/run.md#label)
+  - [Inspecting labels on images or containers](/reference/cli/docker/inspect.md)
+  - [Filtering images by label](/reference/cli/docker/image/ls.md#filter)
+  - [Filtering containers by label](/reference/cli/docker/container/ls.md#filter)
 
 - Local Docker daemons
 
-  - [Adding labels to a Docker daemon at runtime](../reference/cli/dockerd.md)
-  - [Inspecting a Docker daemon's labels](../reference/cli/docker/system/info.md)
+  - [Adding labels to a Docker daemon at runtime](/reference/cli/dockerd.md)
+  - [Inspecting a Docker daemon's labels](/reference/cli/docker/system/info.md)
 
 - Volumes
 
-  - [Adding labels to volumes](../reference/cli/docker/volume/create.md)
-  - [Inspecting a volume's labels](../reference/cli/docker/volume/inspect.md)
-  - [Filtering volumes by label](../reference/cli/docker/volume/ls.md#filter)
+  - [Adding labels to volumes](/reference/cli/docker/volume/create.md)
+  - [Inspecting a volume's labels](/reference/cli/docker/volume/inspect.md)
+  - [Filtering volumes by label](/reference/cli/docker/volume/ls.md#filter)
 
 - Networks
 
-  - [Adding labels to a network](../reference/cli/docker/network/create.md)
-  - [Inspecting a network's labels](../reference/cli/docker/network/inspect.md)
-  - [Filtering networks by label](../reference/cli/docker/network/ls.md#filter)
+  - [Adding labels to a network](/reference/cli/docker/network/create.md)
+  - [Inspecting a network's labels](/reference/cli/docker/network/inspect.md)
+  - [Filtering networks by label](/reference/cli/docker/network/ls.md#filter)
 
 - Swarm nodes
 
-  - [Adding or updating a Swarm node's labels](../reference/cli/docker/node/update.md#label-add)
-  - [Inspecting a Swarm node's labels](../reference/cli/docker/node/inspect.md)
-  - [Filtering Swarm nodes by label](../reference/cli/docker/node/ls.md#filter)
+  - [Adding or updating a Swarm node's labels](/reference/cli/docker/node/update.md#label-add)
+  - [Inspecting a Swarm node's labels](/reference/cli/docker/node/inspect.md)
+  - [Filtering Swarm nodes by label](/reference/cli/docker/node/ls.md#filter)
 
 - Swarm services
-  - [Adding labels when creating a Swarm service](../reference/cli/docker/service/create.md#label)
-  - [Updating a Swarm service's labels](../reference/cli/docker/service/update.md)
-  - [Inspecting a Swarm service's labels](../reference/cli/docker/service/inspect.md)
-  - [Filtering Swarm services by label](../reference/cli/docker/service/ls.md#filter)
+  - [Adding labels when creating a Swarm service](/reference/cli/docker/service/create.md#label)
+  - [Updating a Swarm service's labels](/reference/cli/docker/service/update.md)
+  - [Inspecting a Swarm service's labels](/reference/cli/docker/service/inspect.md)
+  - [Filtering Swarm services by label](/reference/cli/docker/service/ls.md#filter)

content/engine/manage-resources/pruning.md

@@ -5,6 +5,7 @@ keywords: pruning, prune, images, volumes, containers, networks, disk, administr
 title: Prune unused Docker objects
 aliases:
 - /engine/admin/pruning/
+- /config/pruning/
 ---
 
 Docker takes a conservative approach to cleaning up unused objects (often
@@ -51,7 +52,7 @@ $ docker image prune -a --filter "until=24h"
 ```
 
 Other filtering expressions are available. See the
-[`docker image prune` reference](../reference/cli/docker/image/prune.md)
+[`docker image prune` reference](/reference/cli/docker/image/prune.md)
 for more examples.
 
 ## Prune containers
@@ -82,7 +83,7 @@ $ docker container prune --filter "until=24h"
 ```
 
 Other filtering expressions are available. See the
-[`docker container prune` reference](../reference/cli/docker/container/prune.md)
+[`docker container prune` reference](/reference/cli/docker/container/prune.md)
 for more examples.
 
 ## Prune volumes
@@ -110,7 +111,7 @@ $ docker volume prune --filter "label!=keep"
 ```
 
 Other filtering expressions are available. See the
-[`docker volume prune` reference](../reference/cli/docker/volume/prune.md)
+[`docker volume prune` reference](/reference/cli/docker/volume/prune.md)
 for more examples.
 
 ## Prune networks
@@ -139,7 +140,7 @@ $ docker network prune --filter "until=24h"
 ```
 
 Other filtering expressions are available. See the
-[`docker network prune` reference](../reference/cli/docker/network/prune.md)
+[`docker network prune` reference](/reference/cli/docker/network/prune.md)
 for more examples.
 
 ## Prune everything
@@ -187,5 +188,5 @@ $ docker system prune --filter "until=24h"
 ```
 
 Other filtering expressions are available. See the
-[`docker system prune` reference](../reference/cli/docker/system/prune.md)
+[`docker system prune` reference](/reference/cli/docker/system/prune.md)
 for more examples.

content/engine/network/_index.md

@@ -11,6 +11,7 @@ aliases:
 - /engine/userguide/networking/default_network/configure-dns/
 - /engine/userguide/networking/default_network/container-communication/
 - /engine/userguide/networking/dockernetworks/
+- /network/
 ---
 
 Container networking refers to the ability for containers to connect to and
@@ -167,7 +168,7 @@ By default, containers inherit the DNS settings as defined in the
 `/etc/resolv.conf` configuration file.
 Containers that attach to the default `bridge` network receive a copy of this file.
 Containers that attach to a
-[custom network](network-tutorial-standalone.md#use-user-defined-bridge-networks)
+[custom network](tutorials/standalone.md#use-user-defined-bridge-networks)
 use Docker's embedded DNS server.
 The embedded DNS server forwards external DNS lookups to the DNS servers configured on the host.
 
@@ -189,10 +190,10 @@ Your container will have lines in `/etc/hosts` which define the hostname of the
 container itself, as well as `localhost` and a few other common things. Custom
 hosts, defined in `/etc/hosts` on the host machine, aren't inherited by
 containers. To pass additional hosts into a container, refer to [add entries to
-container hosts file](../reference/cli/docker/container/run.md#add-host) in the
+container hosts file](/reference/cli/docker/container/run.md#add-host) in the
 `docker run` reference documentation.
 
 ## Proxy server
 
 If your container needs to use a proxy server, see
-[Use a proxy server](proxy.md).
+[Use a proxy server](/engine/daemon/proxy.md).

content/engine/network/drivers/_index.md

@@ -70,7 +70,7 @@ exist by default, and provide core networking functionality:
 Now that you understand the basics about Docker networks, deepen your
 understanding using the following tutorials:
 
-- [Standalone networking tutorial](../network-tutorial-standalone.md)
-- [Host networking tutorial](../network-tutorial-host.md)
-- [Overlay networking tutorial](../network-tutorial-overlay.md)
-- [Macvlan networking tutorial](../network-tutorial-macvlan.md)
+- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
+- [Host networking tutorial](/engine/network/tutorials/host.md)
+- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
+- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

content/engine/network/drivers/bridge.md

@@ -91,8 +91,8 @@ network.**
     compose file can define the shared variables.
 
   - You can use swarm services instead of standalone containers, and take
-    advantage of shared [secrets](../../engine/swarm/secrets.md) and
-    [configs](../../engine/swarm/configs.md).
+    advantage of shared [secrets](/engine/swarm/secrets.md) and
+    [configs](/engine/swarm/configs.md).
 
 Containers connected to the same user-defined bridge network effectively expose all ports
 to each other. For a port to be accessible to containers or non-Docker hosts on
@@ -132,7 +132,7 @@ daemon. The following table shows which options have equivalent flags in the
 The Docker daemon supports a `--bridge` flag, which you can use to define
 your own `docker0` bridge. Use this option if you want to run multiple daemon
 instances on the same host. For details, see
-[Run multiple daemons](../../reference/cli/dockerd.md#run-multiple-daemons).
+[Run multiple daemons](/reference/cli/dockerd.md#run-multiple-daemons).
 
 ### Default host binding address
 
@@ -166,7 +166,7 @@ $ docker network create my-net
 
 You can specify the subnet, the IP address range, the gateway, and other
 options. See the
-[docker network create](../../reference/cli/docker/network/create.md#specify-advanced-options)
+[docker network create](/reference/cli/docker/network/create.md#specify-advanced-options)
 reference or the output of `docker network create --help` for details.
 
 Use the `docker network rm` command to remove a user-defined bridge
@@ -311,7 +311,7 @@ configured the IP address for the bridge.
 
 ## Next steps
 
-- Go through the [standalone networking tutorial](../network-tutorial-standalone.md)
-- Learn about [networking from the container's point of view](../index.md)
-- Learn about [overlay networks](overlay.md)
-- Learn about [Macvlan networks](macvlan.md)
+- Go through the [standalone networking tutorial](/engine/network/tutorials/standalone.md)
+- Learn about [networking from the container's point of view](../_index.md)
+- Learn about [overlay networks](./overlay.md)
+- Learn about [Macvlan networks](./macvlan.md)

content/engine/network/drivers/host.md

@@ -44,7 +44,7 @@ given swarm node.
 ## Docker Desktop
 
 Host networking is also supported on Docker Desktop version 4.29 and later for Mac,
-Windows, and Linux as a [beta feature](../../release-lifecycle.md#beta). To enable this feature, navigate to the **Features in development** tab in **Settings**, and then select **Enable host networking**.
+Windows, and Linux as a [beta feature](/release-lifecycle.md#beta). To enable this feature, navigate to the **Features in development** tab in **Settings**, and then select **Enable host networking**.
 
 This feature works in both directions. This means you can
 access a server that is running in a container from your host and you can access
@@ -98,8 +98,8 @@ network contradict each other.
 
 ## Next steps
 
-- Go through the [host networking tutorial](../network-tutorial-host.md)
-- Learn about [networking from the container's point of view](../index.md)
-- Learn about [bridge networks](bridge.md)
-- Learn about [overlay networks](overlay.md)
-- Learn about [Macvlan networks](macvlan.md)
+- Go through the [host networking tutorial](/engine/network/tutorials/host.md)
+- Learn about [networking from the container's point of view](../_index.md)
+- Learn about [bridge networks](./bridge.md)
+- Learn about [overlay networks](./overlay.md)
+- Learn about [Macvlan networks](./macvlan.md)

content/engine/network/drivers/ipvlan.md

@@ -11,7 +11,7 @@ The IPvlan driver gives users total control over both IPv4 and IPv6 addressing.
 The VLAN driver builds on top of that in giving operators complete control of
 layer 2 VLAN tagging and even IPvlan L3 routing for users interested in underlay
 network integration. For overlay deployments that abstract away physical constraints
-see the [multi-host overlay](../network-tutorial-overlay.md) driver.
+see the [multi-host overlay](/engine/network/tutorials/overlay.md) driver.
 
 IPvlan is a new twist on the tried and true network virtualization technique.
 The Linux implementations are extremely lightweight because rather than using
@@ -641,4 +641,4 @@ $ ip link del foo
 
 As with all of the Libnetwork drivers, they can be mixed and matched, even as
 far as running 3rd party ecosystem drivers in parallel for maximum flexibility
-to the Docker user.
+to the Docker user.

content/engine/network/drivers/macvlan.md

@@ -107,7 +107,7 @@ $ docker network create -d ipvlan \
 
 ## Use IPv6
 
-If you have [configured the Docker daemon to allow IPv6](../../config/daemon/ipv6.md),
+If you have [configured the Docker daemon to allow IPv6](/engine/daemon/ipv6.md),
 you can use dual-stack IPv4/IPv6 `macvlan` networks.
 
 ```console
@@ -122,4 +122,4 @@ $ docker network create -d macvlan \
 ## Next steps
 
 Learn how to use the Macvlan driver in the
-[Macvlan networking tutorial](../network-tutorial-macvlan.md).
+[Macvlan networking tutorial](/engine/network/tutorials/macvlan.md).

content/engine/network/drivers/none.md

@@ -31,8 +31,8 @@ $ docker run --rm --network none --name no-net-alpine alpine:latest ip addr show
 
 ## Next steps
 
-- Go through the [host networking tutorial](../network-tutorial-host.md)
-- Learn about [networking from the container's point of view](../index.md)
+- Go through the [host networking tutorial](/engine/network/tutorials/host.md)
+- Learn about [networking from the container's point of view](../_index.md)
 - Learn about [bridge networks](bridge.md)
 - Learn about [overlay networks](overlay.md)
-- Learn about [Macvlan networks](macvlan.md)
+- Learn about [Macvlan networks](macvlan.md)

content/engine/network/drivers/overlay.md

@@ -26,7 +26,7 @@ Swarm mode to establish a connection between the hosts.
 
 This page describes overlay networks in general, and when used with standalone
 containers. For information about overlay for Swarm services, see
-[Manage Swarm service networks](../../engine/swarm/networking.md).
+[Manage Swarm service networks](/engine/swarm/networking.md).
 
 ## Create an overlay network
 
@@ -35,8 +35,8 @@ The following table lists ports that need to be open to each host participating
 
 | Ports                  | Description                                                                                                                                                          |
 | :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `2377/tcp`             | The default Swarm control plane port, is configurable with [`docker swarm join --listen-addr`](../../reference/cli/docker/swarm/join.md#--listen-addr-value) |
-| `4789/udp`             | The default overlay traffic port, configurable with [`docker swarm init --data-path-addr`](../../reference/cli/docker/swarm/init.md#data-path-port)          |
+| `2377/tcp`             | The default Swarm control plane port, is configurable with [`docker swarm join --listen-addr`](/reference/cli/docker/swarm/join.md#--listen-addr-value) |
+| `4789/udp`             | The default overlay traffic port, configurable with [`docker swarm init --data-path-addr`](/reference/cli/docker/swarm/init.md#data-path-port)          |
 | `7946/tcp`, `7946/udp` | Used for communication among nodes, not configurable                                                                                                                 |
 
 To create an overlay network that containers on other Docker hosts can connect to,
@@ -124,7 +124,7 @@ For more information about this limitation, see
 
 ## Next steps
 
-- Go through the [overlay networking tutorial](../network-tutorial-overlay.md)
-- Learn about [networking from the container's point of view](../index.md)
+- Go through the [overlay networking tutorial](/engine/network/tutorials/overlay.md)
+- Learn about [networking from the container's point of view](../_index.md)
 - Learn about [standalone bridge networks](bridge.md)
 - Learn about [Macvlan networks](macvlan.md)

content/engine/network/links.md

@@ -6,6 +6,7 @@ title: Legacy container links
 aliases:
 - /userguide/dockerlinks/
 - /engine/userguide/networking/default_network/dockerlinks/
+- /network/links/
 ---
 
 >**Warning**
@@ -415,4 +416,4 @@ root@aed84ee21bde:/opt/webapp# cat /etc/hosts
 172.17.0.7  aed84ee21bde
 <...>
 172.17.0.9  db
-```
+```

content/engine/network/packet-filtering-firewalls.md

@@ -4,6 +4,7 @@ description: How Docker works with packet filtering, iptables, and firewalls
 keywords: network, iptables, firewall
 aliases:
 - /network/iptables/
+- /network/packet-filtering-firewalls/
 ---
 
 On Linux, Docker creates `iptables` and `ip6tables` rules to implement network

content/engine/network/tutorials/host.md

@@ -2,11 +2,13 @@
 title: Networking using the host network
 description: Tutorials for networking using the host network, disabling network isolation
 keywords: networking, host, standalone
+aliases:
+  - /network/network-tutorial-host/
 ---
 
 This series of tutorials deals with networking standalone containers which bind
 directly to the Docker host's network, with no network isolation. For other
-networking topics, see the [overview](index.md).
+networking topics, see the [overview](/engine/network/_index.md).
 
 ## Goal
 
@@ -23,8 +25,8 @@ host.
   Nginx listen on a different port, see the
   [documentation for the `nginx` image](https://hub.docker.com/_/nginx/)
 
-- The `host` networking driver only works on Linux hosts, but is availabe as a
-  [beta feature](../../release-lifecycle.md#beta) on Docker Desktop version 4.29
+- The `host` networking driver only works on Linux hosts, but is available as a
+  [beta feature](/release-lifecycle.md#beta) on Docker Desktop version 4.29
   and later for Mac, Windows, and Linux. To enable this feature, navigate to the
   **Features in development** tab in **Settings**, and then select **Enable host networking**.
 
@@ -63,6 +65,6 @@ host.
 
 ## Other networking tutorials
 
-- [Standalone networking tutorial](network-tutorial-standalone.md)
-- [Overlay networking tutorial](network-tutorial-overlay.md)
-- [Macvlan networking tutorial](network-tutorial-macvlan.md)
+- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
+- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
+- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

content/engine/network/tutorials/macvlan.md

@@ -3,13 +3,15 @@ title: Networking using a macvlan network
 description: Tutorials for networking using a macvlan bridge network and 802.1Q trunk
   bridge network
 keywords: networking, macvlan, 802.1Q, standalone
+aliases:
+  - /network/network-tutorial-macvlan/
 ---
 
 This series of tutorials deals with networking standalone containers which
 connect to `macvlan` networks. In this type of network, the Docker host accepts
 requests for multiple MAC addresses at its IP address, and routes those requests
 to the appropriate container. For other networking topics, see the
-[overview](index.md).
+[overview](/engine/network/_index.md).
 
 ## Goal
 
@@ -218,6 +220,6 @@ be physically attached to the network.
 
 ## Other networking tutorials
 
-- [Standalone networking tutorial](network-tutorial-standalone.md)
-- [Overlay networking tutorial](network-tutorial-overlay.md)
-- [Host networking tutorial](network-tutorial-host.md)
+- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
+- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
+- [Host networking tutorial](/engine/network/tutorials/host.md)

content/engine/network/tutorials/overlay.md

@@ -5,12 +5,13 @@ description: Tutorials for networking with swarm services and standalone contain
 keywords: networking, bridge, routing, ports, swarm, overlay
 aliases:
 - /engine/userguide/networking/get-started-overlay/
+- /network/network-tutorial-overlay/
 ---
 
 This series of tutorials deals with networking for swarm services.
 For networking with standalone containers, see
-[Networking with standalone containers](network-tutorial-standalone.md). If you need to
-learn more about Docker networking in general, see the [overview](index.md).
+[Networking with standalone containers](/engine/network/tutorials/standalone.md). If you need to
+learn more about Docker networking in general, see the [overview](/engine/network/_index.md).
 
 This page includes the following tutorials. You can run each of them on
 Linux, Windows, or a Mac, but for the last one, you need a second Docker
@@ -59,7 +60,7 @@ If you don't have three hosts handy, an easy solution is to set up three
 Ubuntu hosts on a cloud provider such as Amazon EC2, all on the same network
 with all communications allowed to all hosts on that network (using a mechanism
 such as EC2 security groups), and then to follow the
-[installation instructions for Docker Engine - Community on Ubuntu](../engine/install/ubuntu.md).
+[installation instructions for Docker Engine - Community on Ubuntu](/engine/install/ubuntu.md).
 
 ### Walkthrough
 
@@ -436,6 +437,6 @@ example also uses Linux hosts, but the same commands work on Windows.
 
 ## Other networking tutorials
 
-- [Host networking tutorial](network-tutorial-host.md)
-- [Standalone networking tutorial](network-tutorial-standalone.md)
-- [Macvlan networking tutorial](network-tutorial-macvlan.md)
+- [Host networking tutorial](/engine/network/tutorials/host.md)
+- [Standalone networking tutorial](/engine/network/tutorials/standalone.md)
+- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

content/engine/network/tutorials/standalone.md

@@ -2,12 +2,14 @@
 title: Networking with standalone containers
 description: Tutorials for networking with standalone containers
 keywords: networking, bridge, routing, ports, overlay
+aliases:
+  - /network/network-tutorial-standalone/
 ---
 
 This series of tutorials deals with networking for standalone Docker containers.
 For networking with swarm services, see
-[Networking with swarm services](network-tutorial-overlay.md). If you need to
-learn more about Docker networking in general, see the [overview](index.md).
+[Networking with swarm services](/engine/network/tutorials/overlay.md). If you need to
+learn more about Docker networking in general, see the [overview](_index.md).
 
 This topic includes two different tutorials. You can run each of them on
 Linux, Windows, or a Mac, but for the last one, you need a second Docker
@@ -22,9 +24,9 @@ host running elsewhere.
   running on the same Docker host. This is recommended for standalone containers
   running in production.
 
-Although [overlay networks](drivers/overlay.md) are generally used for swarm services,
+Although [overlay networks](/engine/network/drivers/overlay.md) are generally used for swarm services,
 you can also use an overlay network for standalone containers. That's covered as
-part of the [tutorial on using overlay networks](network-tutorial-overlay.md#use-an-overlay-network-for-standalone-containers).
+part of the [tutorial on using overlay networks](/engine/network/tutorials/overlay.md#use-an-overlay-network-for-standalone-containers).
 
 ## Use the default bridge network
 
@@ -615,6 +617,6 @@ connected to both networks.
 
 ## Other networking tutorials
 
-- [Host networking tutorial](network-tutorial-host.md)
-- [Overlay networking tutorial](network-tutorial-overlay.md)
-- [Macvlan networking tutorial](network-tutorial-macvlan.md)
+- [Host networking tutorial](/engine/network/tutorials/host.md)
+- [Overlay networking tutorial](/engine/network/tutorials/overlay.md)
+- [Macvlan networking tutorial](/engine/network/tutorials/macvlan.md)

content/engine/release-notes/17.11.md

@@ -11,7 +11,7 @@ toc_max: 2
 [containerd 1.0 beta](https://github.com/containerd/containerd/releases/tag/v1.0.0-beta.2).
 Docker CE 17.11 and later don't recognize containers started with
 previous Docker versions. If using
-[Live Restore](../../config/containers/live-restore.md),
+[Live Restore](/engine/containers/live-restore.md),
 you must stop all containers before upgrading to Docker CE 17.11.
 If you don't, any containers started by Docker versions that predate
 17.11 aren't recognized by Docker after the upgrade and keep

content/engine/release-notes/18.06.md

@@ -184,7 +184,7 @@ toc_max: 2
 * Set item-type for ExecIDs. [moby/moby#37121](https://github.com/moby/moby/pull/37121)
 * Use go-systemd const instead of magic string in Linux version of dockerd. [moby/moby#37136](https://github.com/moby/moby/pull/37136)
 * Use stdlib TLS dialer. [moby/moby#36687](https://github.com/moby/moby/pull/36687)
-* Warn when an engine label using a reserved namespace (com.docker.\*, io.docker.\*, or org.dockerproject.\*) is configured, as per [Docker object labels](../../config/labels-custom-metadata.md). [moby/moby#36921](https://github.com/moby/moby/pull/36921)
+* Warn when an engine label using a reserved namespace (com.docker.\*, io.docker.\*, or org.dockerproject.\*) is configured, as per [Docker object labels](/engine/manage-resources/labels.md). [moby/moby#36921](https://github.com/moby/moby/pull/36921)
 - Fix missing plugin name in message. [moby/moby#37052](https://github.com/moby/moby/pull/37052)
 - Fix link anchors in CONTRIBUTING.md. [moby/moby#37276](https://github.com/moby/moby/pull/37276)
 - Fix link to Docker Toolbox. [moby/moby#37240](https://github.com/moby/moby/pull/37240)

content/engine/release-notes/18.09.md

@@ -374,7 +374,7 @@ Update your configuration if this command prints a non-empty value for `MountFla
 - Docker has deprecated support for Device Mapper as a storage driver. It will continue to be
 supported at this time, but support will be removed in a future release.
 
-    The [Overlay2 storage driver](../../storage/storagedriver/overlayfs-driver.md) is now the default for Docker engine implementations.
+  The [Overlay2 storage driver](/engine/storage/drivers/overlayfs-driver.md) is now the default for Docker Engine implementations.
 
 For more information on the list of deprecated flags and APIs, have a look at the [deprecation information](/engine/deprecated/) where you can find the target removal dates.
 

content/engine/release-notes/20.10.md

@@ -405,7 +405,7 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
 > longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
 > environment variable for handling requests to `https://` URLs.
 >
-> Refer to [Configure the daemon to use a proxy](../../config/daemon/proxy.md)
+> Refer to [Configure the daemon to use a proxy](/engine/daemon/proxy.md)
 > to learn how to configure the Docker Daemon to use a proxy server.
 { .important }
 
@@ -435,7 +435,7 @@ to learn how to use the `docker scan` command to check if images are vulnerable.
 > longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
 > environment variable for handling requests to `https://` URLs.
 >
-> Refer to the [HTTP/HTTPS proxy section](../../config/daemon/proxy.md#httphttps-proxy)
+> Refer to the [HTTP/HTTPS proxy section](/engine/daemon/proxy.md#httphttps-proxy)
 > to learn how to configure the Docker Daemon to use a proxy server.
 { .important }
 
@@ -476,7 +476,7 @@ well as updated versions of the containerd.io package.
 > longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
 > environment variable for handling requests to `https://` URLs.
 >
-> Refer to the [HTTP/HTTPS proxy section](../../config/daemon/proxy.md#httphttps-proxy)
+> Refer to the [HTTP/HTTPS proxy section](/engine/daemon/proxy.md#httphttps-proxy)
 > to learn how to configure the Docker Daemon to use a proxy server.
 { .important }
 
@@ -521,7 +521,7 @@ well as updated versions of the containerd.io package.
 > longer used for TLS (`https://`) connections. Make sure you also set an `$HTTPS_PROXY`
 > environment variable for handling requests to `https://` URLs.
 >
-> Refer to the [HTTP/HTTPS proxy section](../../config/daemon/proxy.md#httphttps-proxy)
+> Refer to the [HTTP/HTTPS proxy section](/engine/daemon/proxy.md#httphttps-proxy)
 > to learn how to configure the Docker Daemon to use a proxy server.
 { .important }
 

content/engine/release-notes/23.0.md

@@ -468,7 +468,7 @@ To mitigate this, the previous build cache must be discarded. `docker builder pr
 
 #### ipvlan networks ([tracking issue](https://github.com/moby/moby/issues/44925))
 
-When upgrading to the 23.0 branch, the existence of any [ipvlan](../../network/drivers/ipvlan.md) networks will prevent the daemon from starting:
+When upgrading to the 23.0 branch, the existence of any [ipvlan](/engine/network/drivers/ipvlan.md) networks will prevent the daemon from starting:
 
 ```
 panic: interface conversion: interface {} is nil, not string

content/engine/release-notes/25.0.md

@@ -201,7 +201,7 @@ For a full list of pull requests and changes in this release, refer to the relev
 >
 > This option isn't supported with the `-v` or `--volume` flag.
 > For more information, see
-> [Recursive mounts](../../storage/bind-mounts.md#recursive-mounts).
+> [Recursive mounts](/engine/storage/bind-mounts.md#recursive-mounts).
 
 ### New
 

content/engine/security/_index.md

@@ -37,7 +37,7 @@ of another container. Of course, if the host system is setup
 accordingly, containers can interact with each other through their
 respective network interfaces — just like they can interact with
 external hosts. When you specify public ports for your containers or use
-[links](../../network/links.md)
+[links](/engine/network/links.md)
 then IP traffic is allowed between containers. They can ping each other,
 send/receive UDP packets, and establish TCP connections, but that can be
 restricted if necessary. From a network architecture point of view, all
@@ -280,4 +280,4 @@ pull requests, or comments on the Docker community forums.
 * [Seccomp security profiles for Docker](seccomp.md)
 * [AppArmor security profiles for Docker](apparmor.md)
 * [On the Security of Containers (2014)](https://medium.com/@ewindisch/on-the-security-of-containers-2c60ffe25a9e)
-* [Docker swarm mode overlay network security model](../../network/drivers/overlay.md)
+* [Docker swarm mode overlay network security model](/engine/network/drivers/overlay.md)