docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix usage of {% raw%}

This commit is contained in:
Joao Fernandes 2018-04-23 15:57:58 -07:00 committed by Joao Fernandes
parent d4474a39ef
commit 37bb31c591
3 changed files with 16 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ee/dtr/admin/disaster-recovery/create-a-backup.md
View File

@ -13,7 +13,7 @@ keywords: dtr, disaster recovery
Docker Trusted Registry maintains data about: Docker Trusted Registry maintains data about:
| Data | Description | | Data | Description |
|:-----------------------------------|:--------------------------------------------------------------------------------------------------------------------------------------------------| |:-----------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------|
| Configurations | The DTR cluster configurations | | Configurations | The DTR cluster configurations |
| Repository metadata | The metadata about the repositories and images deployed | | Repository metadata | The metadata about the repositories and images deployed |
| Access control to repos and images | Permissions for teams and repositories | | Access control to repos and images | Permissions for teams and repositories |
@ -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, 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): and creating a tar archive of the [dtr-registry volume](../../architecture.md):
{% raw %}
```none ```none
sudo tar -cf {{ image_backup_file }} \ sudo tar -cf {{ image_backup_file }} \
{% raw %}
$(dirname $(docker volume inspect --format '{{.Mountpoint}}' dtr-registry-<replica-id>)) $(dirname $(docker volume inspect --format '{{.Mountpoint}}' dtr-registry-<replica-id>))
{% endraw %}
``` ```
{% endraw %}
If you're using a different storage backend, follow the best practices If you're using a different storage backend, follow the best practices
recommended for that system. recommended for that system.
@ -95,7 +95,7 @@ Where:
This prompts you for the UCP password, backups up the DTR metadata and saves the 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 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. 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 This allows performing backups without affecting your users. Since the replica

6
ee/dtr/admin/disaster-recovery/repair-a-cluster.md
View File

@ -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 You can find the list of replicas by navigating to the UCP web UI, or by using
a UCP client bundle to run: a UCP client bundle to run:
```bash
{% raw %} {% raw %}
```bash
docker ps --format "{{.Names}}" | grep dtr docker ps --format "{{.Names}}" | grep dtr
# The list of DTR containers with <node>/<component>-<replicaID>, e.g. # The list of DTR containers with <node>/<component>-<replicaID>, e.g.
# node-1/dtr-api-a1640e1c15b6 # node-1/dtr-api-a1640e1c15b6
{% endraw %}
``` ```
{% endraw %}
Then, use your UCP client bundle to run the emergency repair command: Then, use your UCP client bundle to run the emergency repair command:
```bash ```bash
{% raw %}
docker run -it --rm {{ page.dtr_org }}/{{ page.dtr_repo }}:{{ page.dtr_version }} emergency-repair \ docker run -it --rm {{ page.dtr_org }}/{{ page.dtr_repo }}:{{ page.dtr_version }} emergency-repair \
--ucp-insecure-tls \ --ucp-insecure-tls \
--existing-replica-id <replica-id> --existing-replica-id <replica-id>
{% endraw %}
``` ```
If the emergency repair procedure is successful, your DTR cluster now has a If the emergency repair procedure is successful, your DTR cluster now has a

4
ee/dtr/admin/disaster-recovery/repair-a-single-replica.md
View File

@ -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 You can find this in the **Stacks** page of the UCP web UI, or by using the UCP
client bundle to run: client bundle to run:
```bash
{% raw %} {% raw %}
```bash
docker ps --format "{{.Names}}" | grep dtr docker ps --format "{{.Names}}" | grep dtr
# The list of DTR containers with <node>/<component>-<replicaID>, e.g. # The list of DTR containers with <node>/<component>-<replicaID>, e.g.
# node-1/dtr-api-a1640e1c15b6 # node-1/dtr-api-a1640e1c15b6
{% endraw %}
``` ```
{% endraw %}
Then use the UCP client bundle to remove the unhealthy replicas: Then use the UCP client bundle to remove the unhealthy replicas: