mirror of https://github.com/docker/docs.git
Remove old UCP/DTR integration topic (#489)
This commit is contained in:
parent
b8c3308206
commit
e2a6d22e87
|
|
@ -1588,8 +1588,6 @@ manuals:
|
||||||
title: Add labels to cluster nodes
|
title: Add labels to cluster nodes
|
||||||
- path: /ee/ucp/admin/configure/add-sans-to-cluster/
|
- path: /ee/ucp/admin/configure/add-sans-to-cluster/
|
||||||
title: Add SANs to cluster certificates
|
title: Add SANs to cluster certificates
|
||||||
- path: /ee/ucp/admin/configure/integrate-with-dtr/
|
|
||||||
title: Integrate with Docker Trusted Registry
|
|
||||||
- path: /ee/ucp/admin/configure/external-auth/
|
- path: /ee/ucp/admin/configure/external-auth/
|
||||||
title: Integrate with LDAP
|
title: Integrate with LDAP
|
||||||
- path: /ee/ucp/admin/configure/external-auth/enable-ldap-config-file/
|
- path: /ee/ucp/admin/configure/external-auth/enable-ldap-config-file/
|
||||||
|
|
|
||||||
|
|
@ -1,153 +0,0 @@
|
||||||
---
|
|
||||||
title: Integrate with Docker Trusted Registry
|
|
||||||
description: Integrate UCP with Docker Trusted Registry
|
|
||||||
keywords: trust, registry, integrate, UCP, DTR
|
|
||||||
ui_tabs:
|
|
||||||
- version: ucp-3.0
|
|
||||||
orhigher: false
|
|
||||||
- version: ucp-2.2
|
|
||||||
orlower: true
|
|
||||||
next_steps:
|
|
||||||
- path: use-your-own-tls-certificates/
|
|
||||||
title: Use your own TLS certificates
|
|
||||||
---
|
|
||||||
{% if include.version=="ucp-3.0" %}
|
|
||||||
|
|
||||||
Once you deploy Docker Trusted Registry (DTR), you can use it to store your
|
|
||||||
Docker images and deploy services to UCP using these images.
|
|
||||||
[Learn how to deploy DTR](/ee/dtr/admin/install/index.md).
|
|
||||||
|
|
||||||
Docker UCP integrates out of the box with Docker Trusted Registry (DTR).
|
|
||||||
This means that you can deploy services from the UCP web UI, using Docker
|
|
||||||
images that are stored in DTR. You can also use a
|
|
||||||
[UCP client bundle](../../user-access/cli.md) to do the same from the
|
|
||||||
CLI.
|
|
||||||
|
|
||||||
If you've configured DTR to use TLS certificates issued by a globally-trusted
|
|
||||||
certificate authority, you can skip this, since all clients will automatically
|
|
||||||
trust the TLS certificates used by DTR.
|
|
||||||
|
|
||||||
If you're using the DTR default configurations or configured DTR to use
|
|
||||||
self-signed certificates, you need to configure all hosts that want to push
|
|
||||||
or pull Docker images from DTR. This includes:
|
|
||||||
|
|
||||||
* All UCP nodes
|
|
||||||
* Your local computer or any other that wants to push or pull Docker images
|
|
||||||
from DTR
|
|
||||||
|
|
||||||
If your host isn't configured to trust the DTR TLS certificates, you'll get an
|
|
||||||
error like:
|
|
||||||
|
|
||||||
```none
|
|
||||||
docker login dtr.example.org
|
|
||||||
|
|
||||||
x509: certificate signed by unknown authority
|
|
||||||
```
|
|
||||||
|
|
||||||
## 1. Configure your local computer
|
|
||||||
|
|
||||||
If you want to use your local computer to interact with DTR, you need to
|
|
||||||
configure it to trust the DTR TLS certificates. This depends on the operating
|
|
||||||
system:
|
|
||||||
|
|
||||||
* For macOS:
|
|
||||||
|
|
||||||
In your browser navigate to `https://<dtr-url>/ca` to download the TLS
|
|
||||||
certificate used by DTR. Then
|
|
||||||
[add this certificate to the macOS trust store](https://support.apple.com/kb/PH18677?locale=en_US).
|
|
||||||
|
|
||||||
* For Windows:
|
|
||||||
|
|
||||||
In your browser navigate to `https://<dtr-url>/ca` to download the TLS
|
|
||||||
certificate used by DTR. Then
|
|
||||||
[add this certificate to the Windows trust store](https://technet.microsoft.com/en-us/library/cc754841(v=ws.11).aspx).
|
|
||||||
|
|
||||||
* For Ubuntu:
|
|
||||||
|
|
||||||
```bash
|
|
||||||
# Download the DTR CA certificate
|
|
||||||
sudo curl -k https://<dtr-url>/ca -o /usr/local/share/ca-certificates/<dtr-domain-name>.crt
|
|
||||||
|
|
||||||
# Refresh the list of certificates to trust
|
|
||||||
sudo update-ca-certificates
|
|
||||||
|
|
||||||
# Restart the Docker daemon
|
|
||||||
sudo service docker restart
|
|
||||||
```
|
|
||||||
|
|
||||||
* For CentOS or RHEL:
|
|
||||||
|
|
||||||
```bash
|
|
||||||
# Download the DTR CA certificate
|
|
||||||
sudo curl -k https://<dtr-url>/ca -o /etc/pki/ca-trust/source/anchors/<dtr-domain-name>.crt
|
|
||||||
|
|
||||||
# Refresh the list of certificates to trust
|
|
||||||
sudo update-ca-trust
|
|
||||||
|
|
||||||
# Restart the Docker daemon
|
|
||||||
sudo /bin/systemctl restart docker.service
|
|
||||||
```
|
|
||||||
|
|
||||||
## 2. Test your local setup
|
|
||||||
|
|
||||||
To confirm that your computer is configured correctly, try to pull and push
|
|
||||||
images from your local Docker installation to DTR.
|
|
||||||
|
|
||||||
1. Create a test repository on DTR.
|
|
||||||
|
|
||||||
Navigate to the **DTR web UI**, and create a new **hello-world** repository
|
|
||||||
so that you can push and pull images. Set it as **private**, and save
|
|
||||||
the changes.
|
|
||||||
|
|
||||||

|
|
||||||
|
|
||||||
2. Pull the `hello-world` image from Docker Store, re-tag it, and push it to the
|
|
||||||
DTR repository you created.
|
|
||||||
|
|
||||||
```none
|
|
||||||
# Pull hello-world from Docker Store
|
|
||||||
docker image pull hello-world:latest
|
|
||||||
|
|
||||||
# Re-tag it
|
|
||||||
docker tag hello-world:latest <dtr-domain>/<user>/hello-world:latest
|
|
||||||
|
|
||||||
# Log into DTR
|
|
||||||
docker login <dtr-domain>
|
|
||||||
|
|
||||||
# Push your image to DTR
|
|
||||||
docker image push <dtr-domain>/<user>/hello-world:latest
|
|
||||||
```
|
|
||||||
|
|
||||||
3. Validate that your image is now stored in DTR.
|
|
||||||
|
|
||||||
When successfully pushing the image you should see a result like:
|
|
||||||
|
|
||||||
```none
|
|
||||||
The push refers to a repository [dtr/username/hello-world]
|
|
||||||
5f70bf18a086: Pushed
|
|
||||||
33e7801ac047: Pushed
|
|
||||||
1: digest: sha256:7d9e482c0cc9e68c7f07bf76e0aafcb1869d32446547909200db990e7bc5461a size: 1930
|
|
||||||
```
|
|
||||||
|
|
||||||
You can also check that the tag exists on the DTR web UI.
|
|
||||||
|
|
||||||

|
|
||||||
|
|
||||||
|
|
||||||
## 3. Configure UCP Docker Engines
|
|
||||||
|
|
||||||
You also need to configure the Docker Engine on every UCP node to trust the
|
|
||||||
DTR TLS certificates. This allows you to deploy services to UCP using images
|
|
||||||
that are stored in DTR.
|
|
||||||
|
|
||||||
For each UCP node:
|
|
||||||
|
|
||||||
1. Log into the node as an administrator, using ssh.
|
|
||||||
2. Configure the system to trust the DTR TLS certificates, following the same
|
|
||||||
steps as you used to configure your local computer.
|
|
||||||
|
|
||||||
{% elsif include.version=="ucp-2.2" %}
|
|
||||||
|
|
||||||
Learn about [integrating with DTR](/datacenter/ucp/2.2/guides/admin/configure/integrate-with-dtr.md).
|
|
||||||
|
|
||||||
{% endif %}
|
|
||||||
Binary file not shown.
|
Before Width: | Height: | Size: 84 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 83 KiB |
Loading…
Reference in New Issue