From 37bb31c591e3e4c4b911642b693f1983d7bfa9c2 Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Mon, 23 Apr 2018 15:57:58 -0700 Subject: [PATCH] Fix usage of {% raw%} --- .../disaster-recovery/create-a-backup.md | 22 +++++++++---------- .../disaster-recovery/repair-a-cluster.md | 6 ++--- .../repair-a-single-replica.md | 6 ++--- 3 files changed, 16 insertions(+), 18 deletions(-) diff --git a/ee/dtr/admin/disaster-recovery/create-a-backup.md b/ee/dtr/admin/disaster-recovery/create-a-backup.md index 912930a192..0d50be597d 100644 --- a/ee/dtr/admin/disaster-recovery/create-a-backup.md +++ b/ee/dtr/admin/disaster-recovery/create-a-backup.md @@ -12,14 +12,14 @@ keywords: dtr, disaster recovery Docker Trusted Registry maintains data about: -| Data | Description | -|:-----------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| -| Configurations | The DTR cluster configurations | -| Repository metadata | The metadata about the repositories and images deployed | -| Access control to repos and images | Permissions for teams and repositories | -| Notary data | Notary tags and signatures | -| Scan results | Security scanning results for images | -| Certificates and keys | The certificates, public keys, and private keys that are used for mutual TLS communication | +| Data | Description | +|:-----------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------| +| Configurations | The DTR cluster configurations | +| Repository metadata | The metadata about the repositories and images deployed | +| Access control to repos and images | Permissions for teams and repositories | +| Notary data | Notary tags and signatures | +| Scan results | Security scanning results for images | +| Certificates and keys | The certificates, public keys, and private keys that are used for mutual TLS communication | | Images content | The images you push to DTR. This can be stored on the file system of the node running DTR, or other storage system, depending on the configuration | This data is persisted on the host running DTR, using named volumes. @@ -60,12 +60,12 @@ If you've configured DTR to store images on the local file system or NFS mount, you can backup the images by using ssh to log into a node where DTR is running, and creating a tar archive of the [dtr-registry volume](../../architecture.md): +{% raw %} ```none sudo tar -cf {{ image_backup_file }} \ -{% raw %} $(dirname $(docker volume inspect --format '{{.Mountpoint}}' dtr-registry-)) -{% endraw %} ``` +{% endraw %} If you're using a different storage backend, follow the best practices recommended for that system. @@ -95,7 +95,7 @@ Where: This prompts you for the UCP password, backups up the DTR metadata and saves the result into a tar archive. You can learn more about the supported flags in -the [reference documentation](../../../../reference/dtr/2.5/cli/backup.md). +the [reference documentation](/reference/dtr/2.5/cli/backup.md). By default the backup command doesn't stop the DTR replica being backed up. This allows performing backups without affecting your users. Since the replica diff --git a/ee/dtr/admin/disaster-recovery/repair-a-cluster.md b/ee/dtr/admin/disaster-recovery/repair-a-cluster.md index ea718ffa2f..3a2a89d700 100644 --- a/ee/dtr/admin/disaster-recovery/repair-a-cluster.md +++ b/ee/dtr/admin/disaster-recovery/repair-a-cluster.md @@ -48,23 +48,21 @@ Start by finding the ID of the DTR replica that you want to repair from. You can find the list of replicas by navigating to the UCP web UI, or by using a UCP client bundle to run: -```bash {% raw %} +```bash docker ps --format "{{.Names}}" | grep dtr # The list of DTR containers with /-, e.g. # node-1/dtr-api-a1640e1c15b6 -{% endraw %} ``` +{% endraw %} Then, use your UCP client bundle to run the emergency repair command: ```bash -{% raw %} docker run -it --rm {{ page.dtr_org }}/{{ page.dtr_repo }}:{{ page.dtr_version }} emergency-repair \ --ucp-insecure-tls \ --existing-replica-id -{% endraw %} ``` If the emergency repair procedure is successful, your DTR cluster now has a diff --git a/ee/dtr/admin/disaster-recovery/repair-a-single-replica.md b/ee/dtr/admin/disaster-recovery/repair-a-single-replica.md index db7d523342..5224219ee3 100644 --- a/ee/dtr/admin/disaster-recovery/repair-a-single-replica.md +++ b/ee/dtr/admin/disaster-recovery/repair-a-single-replica.md @@ -57,14 +57,14 @@ replicas you want to remove. You can find this in the **Stacks** page of the UCP web UI, or by using the UCP client bundle to run: -```bash {% raw %} +```bash docker ps --format "{{.Names}}" | grep dtr # The list of DTR containers with /-, e.g. # node-1/dtr-api-a1640e1c15b6 -{% endraw %} ``` +{% endraw %} Then use the UCP client bundle to remove the unhealthy replicas: @@ -102,4 +102,4 @@ docker run -it --rm \ ## Where to go next -- [Disaster recovery overview](index.md) \ No newline at end of file +- [Disaster recovery overview](index.md)