mirror of https://github.com/docker/docs.git
add todo markers before starting
Signed-off-by: LRubin <lrubin@docker.com>
This commit is contained in:
parent
64041b7224
commit
06f4ddbbc8
|
@ -4,6 +4,8 @@ keywords: docker, registry, dtr, architecture
|
|||
title: DTR architecture
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry (DTR) is a Dockerized application that runs on a Docker
|
||||
Universal Control Plane cluster.
|
||||
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: docker, documentation, about, technology, understanding, configuration
|
|||
title: Configure where images are stored
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
After installing Docker Trusted Registry, one of your first tasks is to
|
||||
designate and configure the Trusted Registry storage backend. This document provides the following:
|
||||
|
||||
|
@ -60,7 +62,7 @@ adequate space available. To do so, you can run the following commands:
|
|||
### Amazon S3
|
||||
|
||||
S3 stores data as objects within “buckets” where you read, write, and delete
|
||||
objects in that container. It too, has a `rootdirectory` parameter. If you select this option, there will be some tasks that you need to first perform [on AWS](https://aws.amazon.com/s3/getting-started/).
|
||||
objects in that container. It too, has a `rootdirectory` parameter. If you select this option, there will be some tasks that you need to first perform [on AWS](https://aws.amazon.com/s3/getting-started/).
|
||||
|
||||
1. You must create an S3 bucket, and write down its name and the AWS zone it
|
||||
runs on.
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: docker, documentation, about, technology, install, enterprise, hub, CS
|
|||
title: Use your own certificates
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
By default the DTR services are exposed using HTTPS, to ensure all
|
||||
communications between clients and DTR is encrypted. Since DTR
|
||||
replicas use self-signed certificates for this, when a client accesses
|
||||
|
|
|
@ -4,6 +4,9 @@ description: Learn how to integrate Docker Trusted Registry with NFS
|
|||
keywords: registry, dtr, storage, nfs
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
|
||||
You can configure DTR to store Docker images in an NFS directory.
|
||||
|
||||
Before installing or configuring DTR to use an NFS directory, make sure that:
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: docker, registry, high-availability, backup, recovery
|
|||
title: Backups and disaster recovery
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
When you decide to start using Docker Trusted Registry on a production
|
||||
setting, you should [configure it for high availability](index.md).
|
||||
|
||||
|
@ -109,7 +111,7 @@ state from an existing backup:
|
|||
$ docker run -i --rm \
|
||||
docker/dtr restore \
|
||||
--ucp-url <ucp-url> \
|
||||
--ucp-insecure-tls \
|
||||
--ucp-insecure-tls \
|
||||
--ucp-username <ucp-admin> \
|
||||
--ucp-password <ucp-password> \
|
||||
--dtr-load-balancer <dtr-domain-name> < /tmp/backup.tar
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, high-availability, backup, recovery
|
|||
title: Set up high availability
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry (DTR) is designed for high availability.
|
||||
|
||||
When you first install DTR, you create a cluster with a single DTR replica.
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, repository, images
|
|||
title: Docker Trusted Registry overview
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry (DTR) is the enterprise-grade image storage solution
|
||||
from Docker. You install it behind your firewall so that you can securely store
|
||||
and manage the Docker images you use in your applications.
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, dtr, registry, install
|
|||
title: Install Docker Trusted Registry
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry (DTR) is a containerized application that runs on a
|
||||
swarm managed by Docker Universal Control Plane (UCP). It can be installed
|
||||
on-premises or on a cloud infrastructure.
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: docker, registry, install, offline
|
|||
title: Install Docker Trusted Registry offline
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
The procedure to install Docker Trusted Registry on a host is the same,
|
||||
whether that host has access to the internet or not.
|
||||
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, dtr, install, license
|
|||
title: License Docker Trusted Registry
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
By default, you don't need to license your Docker Trusted Registry. When
|
||||
installing DTR, it automatically starts using the same license file used on
|
||||
your Docker Universal Control Plane cluster.
|
||||
|
|
|
@ -4,6 +4,8 @@ description: Lean how to scale Docker Trusted Registry by adding and removing re
|
|||
keywords: docker, dtr, install, deploy
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry is designed to scale horizontally as your usage
|
||||
increases. You can add or remove replicas to make DTR scale to your needs
|
||||
or for high availability.
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, DTR, architecture, requirements
|
|||
title: Docker Trusted Registry system requirements
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry can be installed on-premises or on the cloud.
|
||||
Before installing, be sure your infrastructure has these requirements.
|
||||
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, dtr, install, uninstall
|
|||
title: Uninstall Docker Trusted Registry
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Use the `remove` command, to remove a DTR replica from an existing deployment.
|
||||
To uninstall a DTR cluster you remove all DTR replicas one at a time.
|
||||
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, dtr, upgrade, install
|
|||
title: Upgrade DTR
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
The first step in upgrading to a new minor version or patch release of DTR 2.0,
|
||||
is ensuring you're running DTR 2.0. If that's not the case, start by upgrading
|
||||
your installation to version 2.0.0, and then upgrade to the latest version
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, monitor, troubleshoot
|
|||
title: Monitor Docker Trusted Registry
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry is a Dockerized application. To monitor it, you can
|
||||
use the same tools and techniques you're already using to monitor other
|
||||
containerized applications running on your cluster. One way to monitor
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, monitor, troubleshoot
|
|||
title: Troubleshoot Docker Trusted Registry
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
High availability in DTR depends on having overlay networking working in UCP.
|
||||
To manually test that overlay networking is working in UCP run the following
|
||||
commands on two different UCP machines.
|
||||
|
|
|
@ -7,6 +7,8 @@ redirect_from:
|
|||
title: Docker Trusted Registry release notes
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Here you can learn about new features, bug fixes, breaking changes and
|
||||
known issues for each DTR version.
|
||||
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, repository, delete, image
|
|||
title: Delete an image
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
To delete an image, go to the **DTR web UI**, and navigate to the image
|
||||
**repository** you want to delete. In the **Tags** tab, select all the image
|
||||
tags you want to delete, and click the **Delete button**.
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: docker, registry, TLS, certificates
|
|||
title: Configure your Docker Engine
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
By default Docker Engine uses TLS when pushing and pulling images to an
|
||||
image registry like Docker Trusted Registry.
|
||||
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, images, pull
|
|||
title: Pull an image from DTR
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Pulling an image from Docker Trusted Registry is the same as pulling an image
|
||||
from Docker Hub. Since DTR is secure by default, you always need to authenticate
|
||||
before pulling images.
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, images, pull
|
|||
title: Push an image to DTR
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Pushing an image to Docker Trusted Registry is the same as pushing an image
|
||||
to Docker Hub.
|
||||
Since DTR is secure by default, you need to create the image repository before
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: Docker, support, help
|
|||
title: Get support for DTR
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Your Docker Data Center, or Docker Trusted Registry subscription gives you
|
||||
access to prioritized support. The service levels depend on your subscription.
|
||||
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: docker, registry, security, permissions, organizations
|
|||
title: Create and manage organizations
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
When a user creates a repository, only that user has permissions to make changes
|
||||
to the repository.
|
||||
|
||||
|
|
|
@ -5,6 +5,8 @@ keywords: docker, registry, security, permissions, teams
|
|||
title: Create and manage teams
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
You can extend the user's default permissions by granting them fine-grain
|
||||
permissions over image repositories. You do this by adding the user to a team.
|
||||
A team defines the permissions a set of users have for a set of repositories.
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, security, permissions, users
|
|||
title: Create and manage users
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
When using the Docker Datacenter built-in authentication, you can create users
|
||||
to grant them fine-grained permissions.
|
||||
Users are shared across Docker Datacenter. When you create a new user in
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, security, permissions, users
|
|||
title: Authentication and authorization
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
With DTR you get to control which users have access to your image repositories.
|
||||
|
||||
By default, anonymous users can only pull images from public repositories.
|
||||
|
|
|
@ -4,6 +4,8 @@ keywords: docker, registry, security, permissions
|
|||
title: Permission levels
|
||||
---
|
||||
|
||||
<!-- TODO: review page for v2.2 -->
|
||||
|
||||
Docker Trusted Registry allows you to define fine-grain permissions over image
|
||||
repositories.
|
||||
|
||||
|
|
Loading…
Reference in New Issue