Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit e0ad427

Browse files
author
Joao Fernandes
committed
Update DTR install
1 parent e9b670a commit e0ad427

File tree

4 files changed

+37
-67
lines changed

4 files changed

+37
-67
lines changed

datacenter/dtr/2.1/architecture.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -43,13 +43,14 @@ are created:
4343

4444
DTR uses these named volumes for persisting data:
4545

46-
| Volume name | Description |
47-
|:--------------------------------|:---------------------------------------------------------------------------------|
48-
| dtr-ca-<replica_id> | Root key material for the DTR root CA that issues certificates |
49-
| dtr-etcd-<replica_id> | DTR configuration data |
50-
| dtr-notary-<replica_id> | Certificate and keys for the Notary components |
51-
| dtr-registry-<replica_id> | Docker images data, if DTR is configured to store images on the local filesystem |
52-
| dtr-rethink-<replica_id> | Repository metadata |
46+
| Volume name | Description |
47+
|:------------------------------------|:---------------------------------------------------------------------------------|
48+
| dtr-ca-<replica_id> | Root key material for the DTR root CA that issues certificates |
49+
| dtr-etcd-<replica_id> | DTR configuration data |
50+
| dtr-notary-<replica_id> | Certificate and keys for the Notary components |
51+
| dtr-registry-<replica_id> | Docker images data, if DTR is configured to store images on the local filesystem |
52+
| dtr-rethink-<replica_id> | Repository metadata |
53+
| dtr-nfs-registry-<replica_id> | Docker images data, if DTR is configured to store images on NFS |
5354

5455
You can customize the volume driver used for these volumes, by creating the
5556
volumes before installing DTR. During the installation, DTR checks which volumes

datacenter/dtr/2.1/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ DTR uses the same authentication mechanism as Docker Universal Control Plane.
2727
It has a built-in authentication mechanism, and also integrates with LDAP
2828
and Active Directory. It also supports Role Based Access Control (RBAC).
2929

30-
This allows you to implement fine-grain access control policies, on who has
30+
This allows you to implement fine-grain access control policies on who has
3131
access to your Docker images.
3232

3333
![](images/overview-2.png)

datacenter/dtr/2.1/install/index.md

Lines changed: 27 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -29,73 +29,42 @@ Make sure all the nodes you plan on installing DTR are being managed by UCP.
2929
To install DTR you use the `docker/dtr` image. This image has commands to
3030
install, configure, and backup DTR.
3131

32-
To install DTR:
32+
Run the following command to install DTR:
3333

34-
1. Get the DTR package.
34+
```bash
35+
# Pull the latest version of DTR
36+
$ docker pull docker/dtr
3537

36-
```bash
37-
$ wget https://packages.docker.com/caas/ucp-2.0.0-beta3_dtr-2.1.0-beta3.tar.gz -O docker-datacenter.tar.gz
38-
```
39-
40-
2. Transfer the package to the nodes.
38+
# Install DTR
39+
$ docker run -it --rm \
40+
docker/dtr install \
41+
--ucp-node <ucp-node-name> \
42+
--ucp-insecure-tls
43+
```
4144

42-
Now that you have the DTR package in your machine, you can transfer it to the
43-
nodes that you want to install DTR. For each node run:
44-
45-
```bash
46-
$ scp docker-datacenter.tag.gz <user>@<host>:/tmp
47-
```
48-
49-
3. Load the images.
50-
51-
Once the package is on the nodes where you want to install DTR, you can use
52-
the `docker load` command, to load the images from the .tar file. Log
53-
into each node where you plan on installing DTR and run:
54-
55-
```bash
56-
$ docker load < /tmp/docker-datacenter.tar.gz
57-
```
45+
Where the `--ucp-node` is the hostname of the UCP node where you want to deploy
46+
DTR. `--ucp-insecure-tls` tells the installer to trust the certificates used
47+
by UCP.
5848

59-
4. Download a UCP client bundle.
49+
The install command has other flags for customizing DTR at install time.
50+
Check the [reference documentation to learn more](../reference/install.md).
6051

61-
Having a UCP client bundle allows you to run Docker commands on a swarm
62-
being managed by UCP.
63-
[Download a UCP client bundle](https://docs.docker.com/ucp/access-ucp/cli-based-access/)
64-
and set up your CLI client to use it.
6552

66-
5. Run the following commands to install DTR.
53+
## Step 4. Check that DTR is running
6754

68-
```bash
69-
70-
# Install DTR
71-
$ docker run -it --rm \
72-
docker/dtr:2.1.0-beta3 install \
73-
--ucp-node <hostname> \
74-
--ucp-insecure-tls
75-
```
76-
77-
Where the `--ucp-node` is the hostname of the node where you've previously
78-
loaded the DTR images, and `--ucp-insecure-tls` tells the installer to
79-
trust the certificates used by UCP.
80-
The install command has other flags for customizing DTR at install time.
81-
Check the [reference documentation to learn more](../reference/install.md).
82-
83-
84-
6. Check that DTR is running.
85-
86-
In your browser, navigate to the the Docker **Universal Control Plane**
87-
web UI, and navigate to the **Applications** screen. DTR should be listed
88-
as an application.
55+
In your browser, navigate to the the Docker **Universal Control Plane**
56+
web UI, and navigate to the **Applications** screen. DTR should be listed
57+
as an application.
8958

90-
![](../images/install-dtr-1.png)
59+
![](../images/install-dtr-1.png)
9160

92-
You can also access the **DTR web UI**, to make sure it is working. In your
93-
browser, navigate to the address were you installed DTR.
61+
You can also access the **DTR web UI**, to make sure it is working. In your
62+
browser, navigate to the address were you installed DTR.
9463

95-
![](../images/install-dtr-2.png)
64+
![](../images/install-dtr-2.png)
9665

9766

98-
## Step 4. Configure DTR
67+
## Step 5. Configure DTR
9968

10069
After installing DTR, you should configure:
10170

@@ -107,13 +76,13 @@ After installing DTR, you should configure:
10776

10877
![](../images/install-dtr-3.png)
10978

110-
## Step 5. Test pushing and pulling
79+
## Step 6. Test pushing and pulling
11180

11281
Now that you have a working installation of DTR, you should test that you can
11382
push and pull images to it.
11483
[Learn how to push and pull images](../repos-and-images/index.md).
11584

116-
## Step 6. Join replicas to the cluster
85+
## Step 7. Join replicas to the cluster
11786

11887
This step is optional.
11988

@@ -143,7 +112,7 @@ replicas:
143112
```bash
144113
$ docker run -it --rm \
145114
docker/dtr:2.1.0-beta3 join \
146-
--ucp-node <hostname> \
115+
--ucp-node <ucp-node-name> \
147116
--ucp-insecure-tls
148117
```
149118

datacenter/dtr/2.1/install/install-offline.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ copy that package to the nodes where you’ll install DTR.
2020
Docker Datacenter components:
2121

2222
```bash
23-
$ wget https://packages.docker.com/caas/ucp-2.0.0-beta3_dtr-2.1.0-beta3.tar.gz -O docker-datacenter.tar.gz
23+
$ wget https://packages.docker.com/caas/ucp-2.0.0_dtr-2.1.0.tar.gz -O docker-datacenter.tar.gz
2424
```
2525

2626
2. Transfer the package to the offline nodes.

0 commit comments

Comments
 (0)