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

Update DTR 2.3 variables

This commit is contained in:
Joao Fernandes 2017-07-05 11:57:28 -07:00 committed by Jim Galasyn
parent c03209fca9
commit c70a713b61
11 changed files with 39 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
_config.yml
View File

@ -103,9 +103,8 @@ defaults:
- scope:
path: "datacenter/dtr/2.3"
values:
ucp_version: "2.2"
dtr_version: "2.3"
docker_image: "docker/dtr:2.3.0"
dtr_version_minor: "2.3"
dtr_version_patch: "2.3.0"
- scope:
path: "datacenter/dtr/2.2"
values:

38
datacenter/dtr/2.3/guides/admin/backups-and-disaster-recovery.md
View File

@ -4,6 +4,9 @@ description: Learn how to back up your Docker Trusted Registry cluster, and to r
keywords: docker, registry, high-availability, backup, recovery
---
{% assign image_backup_file = "backup-images.tar" %}
{% assign metadata_backup_file = "backup-metadata.tar" %}
DTR needs that a majority (n/2 + 1) of its replicas are healthy at all times
for it to work. So if a majority of replicas is unhealthy or lost, the only
way to restore DTR to a working state, is by recovering from a backup. This
@ -32,12 +35,12 @@ command backups up the following data:
| Data | Backed up | Description |
|:-----------------------------------|:----------|:---------------------------------------------------------------|
| Configurations | yes | |
| Repository metadata | yes | |
| Access control to repos and images | yes | |
| Notary data | yes | |
| Scan results | yes | |
| Certificates and keys | yes | |
| Configurations | yes | DTR settings |
| Repository metadata | yes | Metadata like image architecture and size |
| Access control to repos and images | yes | Data about who has access to which images |
| Notary data | yes | Signatures and digests for images that are signed |
| Scan results | yes | Information about vulnerabilities in your images |
| Certificates and keys | yes | TLS certificates and keys used by DTR |
| Image content | no | Needs to be backed up separately, depends on DTR configuration |
| Users, orgs, teams | no | Create a UCP backup to backup this data |
| Vulnerability database | no | Can be re-downloaded after a restore |
@ -63,7 +66,8 @@ 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):
```none
tar -cf /tmp/backup-images.tar dtr-registry-<replica-id>
sudo tar -cf {{ image_backup_file }} \
$(dirname $(docker volume inspect --format '{{.Mountpoint}}' dtr-registry-<replica-id>))
```
If you're using a different storage backend, follow the best practices
@ -79,16 +83,15 @@ command, replacing the placeholders for the real values:
read -sp 'ucp password: ' UCP_PASSWORD; \
docker run -i --rm \
--env UCP_PASSWORD=$UCP_PASSWORD \
docker/dtr:<version> backup \
docker/dtr:{{ page.dtr_version_patch }} backup \
--ucp-url <ucp-url> \
--ucp-insecure-tls \
--ucp-username <ucp-username> \
--existing-replica-id <replica-id> > /tmp/backup-metadata.tar
--existing-replica-id <replica-id> > backup-metadata.tar
```
Where:
* `<version>`, the version of DTR you're running
* `<ucp-url>` is the url you use to access UCP
* `<ucp-username>` is the username of a UCP administrator
* `<replica-id>` is the id of the DTR replica to backup
@ -103,7 +106,7 @@ without affecting your users. Also, the backup contains sensitive information
like private keys, so you can encrypt the backup by running:
```none
gpg --symmetric /tmp/backup-metadata.tar
gpg --symmetric {{ backup-metadata.tar }}
```
This prompts you for a password to encrypt the backup, copies the backup file
@ -115,7 +118,7 @@ To validate that the backup was correctly performed, you can print the contents
of the tar file created. The backup of the images should look like:
```none
tar -tf /tmp/backup-images.tar
tar -tf {{ image_backup_file }}
dtr-backup-v2.2.3/
dtr-backup-v2.2.3/rethink/
@ -125,7 +128,7 @@ dtr-backup-v2.2.3/rethink/layers/
And the backup of the DTR metadata should look like:
```none
tar -tf /tmp/backup-metadata.tar
tar -tf {{ backup-metadata.tar }}
# The archive should look like this
dtr-backup-v2.2.1/
@ -171,7 +174,7 @@ Start by removing any DTR container that is still running:
```none
docker run -it --rm \
docker/dtr:<version> destroy \
docker/dtr:{{ page.dtr_version_patch }} destroy \
--ucp-insecure-tls
```
@ -181,7 +184,7 @@ If you had DTR configured to store images on the local filesystem, you can
extract your backup:
```none
sudo tar -xzf /tmp/image-backup.tar -C /var/lib/docker/volumes
sudo tar -xzf {{ image_backup_file }} -C /var/lib/docker/volumes
```
If you're using a different storage backend, follow the best practices
@ -202,18 +205,17 @@ placeholders for the real values:
read -sp 'ucp password: ' UCP_PASSWORD; \
docker run -i --rm \
--env UCP_PASSWORD=$UCP_PASSWORD \
docker/dtr:<version> restore \
docker/dtr:{{ page.dtr_version_patch }} restore \
--ucp-url <ucp-url> \
--ucp-insecure-tls \
--ucp-username <ucp-username> \
--ucp-node <hostname> \
--replica-id <replica-id> \
--dtr-external-url <dtr-external-url> < /tmp/backup-metadata.tar
--dtr-external-url <dtr-external-url> < {{ metadata_backup_file }}
```
Where:
* `<version>`, the version of DTR you're running
* `<ucp-url>` is the url you use to access UCP
* `<ucp-username>` is the username of a UCP administrator
* `<hostname>` is the hostname of the node where you've restored the images

4
datacenter/dtr/2.3/guides/admin/configure/create-and-manage-orgs.md
View File

@ -1,12 +1,10 @@
---
title: Create and manage organizations in DTR
description: Learn how to set up organizations to enforce security in Docker Trusted
Registry.
keywords: docker, registry, security, permissions, organizations
title: Create and manage organizations in DTR
---
<!-- TODO: review page for v2.2 -->
When a user creates a repository, only that user has permissions to make changes
to the repository.

5
datacenter/dtr/2.3/guides/admin/configure/deploy-caches/index.md
View File

@ -2,10 +2,9 @@
title: Deploy DTR caches
description: Learn how to deploy and configure DTR caches, so that users can pull images faster.
keywords: docker, registry, dtr, cache
redirect_from:
- /datacenter/dtr/2.2/guides/admin/configure/deploy-a-cache/
---
You can configure DTR to have multiple caches. Once you've deployed caches,
users can configure their DTR user account to specify which cache to pull from.
@ -185,7 +184,7 @@ docker run --detach --restart always \
--publish 5000:5000 \
--volume $(pwd)/dtr-ca.pem:/certs/dtr-ca.pem \
--volume $(pwd)/config.yml:/config.yml \
docker/dtr-content-cache:<version> /config.yml
docker/dtr-content-cache:{{ page.dtr_version_patch }} /config.yml
```
You can also run the command in interactive mode instead of detached by

4
datacenter/dtr/2.3/guides/admin/configure/set-up-high-availability.md
View File

@ -50,7 +50,7 @@ To add replicas to an existing DTR deployment:
```none
docker run -it --rm \
{{ page.docker_image }} join \
docker/dtr:{{ page.dtr_version_patch }} join \
--ucp-node <ucp-node-name> \
--ucp-insecure-tls
```
@ -70,7 +70,7 @@ To remove a DTR replica from your deployment:
```none
docker run -it --rm \
{{ page.docker_image }} remove \
docker/dtr:{{ page.dtr_version_patch }} remove \
--ucp-insecure-tls
```

6
datacenter/dtr/2.3/guides/admin/install/index.md
View File

@ -36,11 +36,11 @@ Run the following command to install DTR:
```none
# Pull the latest version of DTR
$ docker pull {{ page.docker_image }}
$ docker pull docker/dtr{{ page.dtr_version_patch }}
# Install DTR
$ docker run -it --rm \
{{ page.docker_image }} install \
docker/dtr:{{ page.dtr_version_patch }} install \
--ucp-node <ucp-node-name> \
--ucp-insecure-tls
```
@ -119,7 +119,7 @@ To add replicas to a DTR cluster, use the `docker/dtr join` command:
```none
docker run -it --rm \
{{ page.docker_image }} join \
docker/dtr:{{ page.dtr_version_patch }} join \
--ucp-node <ucp-node-name> \
--ucp-insecure-tls
```

2
datacenter/dtr/2.3/guides/admin/install/uninstall.md
View File

@ -9,7 +9,7 @@ replica. To do that, you just run the destroy command once per replica:
```none
docker run -it --rm \
{{ page.docker_image }} destroy \
docker/dtr:{{ page.dtr_version_patch }} destroy \
--ucp-insecure-tls
```

4
datacenter/dtr/2.3/guides/admin/monitor-and-troubleshoot/troubleshoot-with-logs.md
View File

@ -74,7 +74,7 @@ and join a new one. Start by running:
```none
docker run -it --rm \
{{ page.docker_image }} remove \
docker/dtr:{{ page.dtr_version_patch }} remove \
--ucp-insecure-tls
```
@ -82,7 +82,7 @@ And then:
```none
docker run -it --rm \
{{ page.docker_image }} join \
docker/dtr:{{ page.dtr_version_patch }} join \
--ucp-node <ucp-node-name> \
--ucp-insecure-tls
```

4
datacenter/dtr/2.3/guides/admin/upgrade.md
View File

@ -56,7 +56,7 @@ Make sure you're running DTR 2.1. If that's not the case, [upgrade your installa
Then pull the latest version of DTR:
```none
$ docker pull {{ page.docker_image }}
$ docker pull docker/dtr:{{ page.dtr_version_patch }}
```
If the node you're upgrading doesn't have access to the internet, you can
@ -68,7 +68,7 @@ nodes if upgrading offline), run the upgrade command:
```none
$ docker run -it --rm \
{{ page.docker_image }} upgrade \
docker/dtr{{ page.dtr_version_patch }} upgrade \
--ucp-insecure-tls
```

4
datacenter/dtr/2.3/guides/release-notes/incompatibilities-and-breaking-changes.md
View File

@ -1,11 +1,11 @@
---
title: Incompatibilities and breaking changes
description: Learn about the incompatibilities and breaking changes introduced by Docker Trusted Registry version {{ page.dtr_version }}
description: Learn about the incompatibilities and breaking changes introduced by Docker Trusted Registry version {{ page.dtr_version_minor }}
keywords: docker, ucp, upgrade, incompatibilities
redirect_from:
- /datacenter/dtr/2.2/guides/admin/upgrade/incompatibilities-and-breaking-changes/
---
With Docker Trusted Registry {{ page.dtr_version }}, the `/load_balancer_status`
With Docker Trusted Registry {{ page.dtr_version_minor }}, the `/load_balancer_status`
endpoint is deprecated and is going to be removed in future versions. Use the
`/health` endpoint instead.

4
datacenter/dtr/2.3/guides/release-notes/index.md
View File

@ -1,6 +1,6 @@
---
title: DTR 2.2 release notes
description: Learn about the new features, bug fixes, and breaking changes for Docker Trusted Registry {{ page.dtr_version }}
title: DTR {{ page.dtr_version_minor }} release notes
description: Learn about the new features, bug fixes, and breaking changes for Docker Trusted Registry {{ page.dtr_version_minor }}
keywords: docker trusted registry, whats new, release notes
redirect_from:
- /datacenter/dtr/2.2/guides/admin/upgrade/release-notes/