diff --git a/ee/admin/backup/back-up-swarm.md b/ee/admin/backup/back-up-swarm.md index e019038e90..dbc693047a 100644 --- a/ee/admin/backup/back-up-swarm.md +++ b/ee/admin/backup/back-up-swarm.md @@ -27,7 +27,7 @@ You must perform a manual backup on each manager node, because logs contain node 1. Retrieve your Swarm unlock key if `auto-lock` is enabled to be able to restore the swarm from backup. Retrieve the unlock key if necessary and store it in a safe location. If you are unsure, read - [Lock your swarm to protect its encryption key](/engine/swarm/swarm_manager_locking.md). + [Lock your swarm to protect its encryption key](../../../engine/swarm/swarm_manager_locking.md). 2. Because you must stop the engine of the manager node before performing the backup, having three manager nodes is recommended for high availability (HA). For a cluster to be operational, a majority of managers @@ -80,5 +80,5 @@ You must perform a manual backup on each manager node, because logs contain node ### Where to go next -- [Back up UCP](back-up-ucp) +- [Back up UCP](back-up-ucp.md) diff --git a/ee/admin/backup/back-up-ucp.md b/ee/admin/backup/back-up-ucp.md index 6e35668f4c..61c1adbba5 100644 --- a/ee/admin/backup/back-up-ucp.md +++ b/ee/admin/backup/back-up-ucp.md @@ -259,5 +259,5 @@ The following table describes the backup schema returned by the `GET` and `LIST` ### Where to go next -- [Back up the Docker Trusted Registry](./back-up-dtr/) +- [Back up the Docker Trusted Registry](back-up-dtr.md) diff --git a/ee/admin/backup/index.md b/ee/admin/backup/index.md index c172628a2f..39190edc0d 100644 --- a/ee/admin/backup/index.md +++ b/ee/admin/backup/index.md @@ -22,9 +22,9 @@ This document provides instructions and best practices for Docker Enterprise bac To back up Docker Enterprise, you must create individual backups for each of the following components: -1. [Back up Docker Swarm](back-up-swarm). Back up Swarm resources like service and network definitions. -2. [Back up Universal Control Plane (UCP)](back-up-ucp). Back up UCP configurations. -3. [Back up Docker Trusted Registry (DTR)](back-up-dtr). Back up DTR configurations, images, and metadata. +1. [Back up Docker Swarm](back-up-swarm.md). Back up Swarm resources like service and network definitions. +2. [Back up Universal Control Plane (UCP)](back-up-ucp.md). Back up UCP configurations. +3. [Back up Docker Trusted Registry (DTR)](back-up-dtr.md). Back up DTR configurations, images, and metadata. If you do not create backups for all components, you cannot restore your deployment to its previous state. @@ -35,4 +35,4 @@ a fresh installation on a separate infrastructure with the backup. Refer to [Res ### Where to go next -- [Back up Docker Swarm](./back-up-swarm/) +- [Back up Docker Swarm](back-up-swarm.md) diff --git a/ee/admin/restore/index.md b/ee/admin/restore/index.md index 05d09e6540..608f9b2db4 100644 --- a/ee/admin/restore/index.md +++ b/ee/admin/restore/index.md @@ -10,10 +10,10 @@ swarm and join new ones to bring the swarm to an healthy state. Restore components individually and in the following order: -1. [Restore Docker Swarm](restore-swarm). -2. [Restore Universal Control Plane (UCP)](restore-ucp). -3. [Restore Docker Trusted Registry (DTR)](restore-dtr). +1. [Restore Docker Swarm](restore-swarm.md). +2. [Restore Universal Control Plane (UCP)](restore-ucp.md). +3. [Restore Docker Trusted Registry (DTR)](restore-dtr.md). ## Where to go next -- [Restore Docker Swarm](restore-swarm) +- [Restore Docker Swarm](restore-swarm.md) diff --git a/ee/admin/restore/restore-swarm.md b/ee/admin/restore/restore-swarm.md index 090bcd6fdc..448edde20a 100644 --- a/ee/admin/restore/restore-swarm.md +++ b/ee/admin/restore/restore-swarm.md @@ -50,4 +50,4 @@ Use the following procedure on each manager node to restore data to a new swarm. ### Where to go next -- [Restore UCP](restore-ucp) +- [Restore UCP](restore-ucp.md) diff --git a/ee/admin/restore/restore-ucp.md b/ee/admin/restore/restore-ucp.md index 9581a62ba4..b4c4f5f2cd 100644 --- a/ee/admin/restore/restore-ucp.md +++ b/ee/admin/restore/restore-ucp.md @@ -99,4 +99,4 @@ Alternatively, check the UCP UI **Nodes** page for node status, and monitor the ### Where to go next -- [Restore DTR](restore-dtr) +- [Restore DTR](restore-dtr.md) diff --git a/ee/cluster/aws.md b/ee/cluster/aws.md index 1e7f6544a2..b3385fcd26 100644 --- a/ee/cluster/aws.md +++ b/ee/cluster/aws.md @@ -389,6 +389,6 @@ All provisioned resources are destroyed and the context for the cluster is remov ## Where to go next -- View the quick start guide for [Azure](azure.md) or [vSphere](vsphere.md) +- View the quick start guide for [Azure](azure.md) - [Explore the full list of Cluster commands](/engine/reference/commandline/cluster/) -- [Cluster configuration file reference](/ee/cluster-file.md) +- [Cluster configuration file reference](cluster-file.md) diff --git a/ee/cluster/azure.md b/ee/cluster/azure.md index e0506578de..cb93b50709 100644 --- a/ee/cluster/azure.md +++ b/ee/cluster/azure.md @@ -402,5 +402,5 @@ When the cluster has reached end-of-life, run `docker cluster rm quickstart` ## Where to go next -- [Explore the full list of Cluster commands](./reference/index.md) -- [Cluster configuration file reference](/ee/cluster-file/index.md) +- [Explore the full list of Cluster commands](/engine/reference/commandline/cluster/) +- [Cluster configuration file reference](cluster-file.md) diff --git a/ee/cluster/index.md b/ee/cluster/index.md index e24504aa7d..acb0293ccf 100644 --- a/ee/cluster/index.md +++ b/ee/cluster/index.md @@ -74,5 +74,5 @@ docker container rm dci - [Get started with Docker Cluster on AWS](aws.md) - [Command line reference](/engine/reference/commandline/cluster/) -- [Cluster file reference](/ee/cluster-file.md) +- [Cluster file reference](cluster-file.md) diff --git a/ee/docker-ee-architecture.md b/ee/docker-ee-architecture.md index be5a5f4b5e..082cbcb939 100644 --- a/ee/docker-ee-architecture.md +++ b/ee/docker-ee-architecture.md @@ -75,7 +75,7 @@ directly. Instead, you interact with UCP. Since UCP exposes the standard Docker API and the full Kubernetes API transparently, you can use the tools you already know and love, like `kubectl`, the Docker CLI client, and Docker Compose. -[Learn about UCP architecture](/ee/ucp/ucp-architecture.md). +[Learn about UCP architecture](ucp/ucp-architecture.md). ![](/ee/ucp/images/ucp-architecture-2.svg){: .with-border} @@ -96,9 +96,9 @@ worker node. All DTR replicas run the same set of services, and changes to their configuration are automatically propagated to other replicas. -[Learn about DTR architecture](/ee/dtr/architecture.md). +[Learn about DTR architecture](dtr/architecture.md). ## Where to go next -- [UCP architecture](/ee/ucp/ucp-architecture.md) -- [DTR architecture](/ee/dtr/architecture.md) +- [UCP architecture](ucp/ucp-architecture.md) +- [DTR architecture](dtr/architecture.md) diff --git a/ee/docker-ee/centos.md b/ee/docker-ee/centos.md index c09c2ce367..24c27edd64 100644 --- a/ee/docker-ee/centos.md +++ b/ee/docker-ee/centos.md @@ -29,7 +29,7 @@ Shared between centOS.md, rhel.md, oracle.md ---> For Docker Community Edition on {{ linux-dist-cap }}, see -[Install Docker Engine on CentOS](/engine/install/centos.md). +[Install Docker Engine on CentOS](../../engine/install/centos.md). ## Prerequisites @@ -53,7 +53,7 @@ On {{ linux-dist-long }}, Docker Engine - Enterprise supports storage drivers, higher, `overlay2` is the recommended storage driver. The following limitations apply: -- [OverlayFS](/storage/storagedriver/overlayfs-driver){: target="_blank" class="_" }: +- [OverlayFS](/storage/storagedriver/overlayfs-driver/){: target="_blank" class="_" }: If `selinux` is enabled, the `overlay2` storage driver is supported on {{ linux-dist-cap }} 7.4 or higher. If `selinux` is disabled, `overlay2` is supported on {{ linux-dist-cap }} 7.2 or higher with kernel version 3.10.0-693 @@ -220,7 +220,7 @@ Shared between centOS.md, oracle.md ``` Docker Engine - Enterprise is installed and running. Use `sudo` to run Docker commands. See - [Linux postinstall](/engine/install/linux-postinstall.md){: target="_blank" class="_" } to allow + [Linux postinstall](../../engine/install/linux-postinstall.md){: target="_blank" class="_" } to allow non-privileged users to run Docker commands.