mirror of https://github.com/docker/docs.git
Updating per Betty's verbal comments.
Entering Betty's second round comment Fix awkward code blips Merging JChu's comments from outdated material Fixing problems in Dockerfile pdating with the comments from John Updating for DTR Updating for fix Updating with the comments from Betty and Jon Signed-off-by: Mary Anthony <mary@docker.com>
This commit is contained in:
Mary Anthony
parent
dbdff7a3da
commit
a27fb2ff0d
33
Dockerfile
33
Dockerfile
|
|
@ -1,27 +1,18 @@
|
|||
FROM docs/base:hugo-github-linking
|
||||
MAINTAINER Mary Anthony <mary@docker.com> (@moxiegirl)
|
||||
|
||||
RUN svn checkout https://github.com/docker/tutorials/trunk/docs/mac /docs/content/mac \
|
||||
&& svn checkout https://github.com/docker/tutorials/trunk/docs/windows /docs/content/windows \
|
||||
&& svn checkout https://github.com/docker/tutorials/trunk/docs/linux /docs/content/linux
|
||||
|
||||
RUN svn checkout https://github.com/docker/docker/trunk/docs /docs/content/
|
||||
|
||||
RUN svn checkout https://github.com/docker/compose/trunk/docs /docs/content/compose \
|
||||
&& svn checkout https://github.com/docker/swarm/trunk/docs /docs/content/swarm \
|
||||
&& svn checkout https://github.com/docker/machine/trunk/docs /docs/content/machine \
|
||||
&& svn checkout https://github.com/docker/distribution/trunk/docs /docs/content/registry \
|
||||
&& svn checkout https://github.com/kitematic/kitematic/trunk/docs /docs/content/kitematic \
|
||||
&& svn checkout https://github.com/docker/opensource/trunk/docs /docs/content/opensource
|
||||
|
||||
# To get the git info for this repo
|
||||
COPY . /src
|
||||
|
||||
COPY . /docs/content/docker-trusted-registry/
|
||||
COPY . /docs/content/docker-trusted-registry
|
||||
|
||||
|
||||
RUN wget https://raw.githubusercontent.com/docker/docs.docker.com/master/touch-up.sh
|
||||
RUN chmod 777 touch-up.sh && mv touch-up.sh /src && cat /dev/null > /docs/build.json
|
||||
|
||||
# To get the git info for this repo
|
||||
|
||||
RUN /src/touch-up.sh /docs
|
||||
RUN svn checkout https://github.com/docker/docker/trunk/docs /docs/content/engine
|
||||
RUN svn checkout https://github.com/docker/compose/trunk/docs /docs/content/compose
|
||||
RUN svn checkout https://github.com/docker/swarm/trunk/docs /docs/content/swarm
|
||||
RUN svn checkout https://github.com/docker/machine/trunk/docs /docs/content/machine
|
||||
RUN svn checkout https://github.com/docker/distribution/trunk/docs /docs/content/registry
|
||||
RUN svn checkout https://github.com/kitematic/kitematic/trunk/docs /docs/content/kitematic
|
||||
RUN svn checkout https://github.com/docker/tutorials/trunk/docs/mac /docs/content/mac
|
||||
RUN svn checkout https://github.com/docker/tutorials/trunk/docs/windows /docs/content/windows
|
||||
RUN svn checkout https://github.com/docker/tutorials/trunk/docs/linux /docs/content/linux
|
||||
RUN svn checkout https://github.com/docker/opensource/trunk/docs /docs/content/opensource
|
||||
|
|
|
|||
2
index.md
2
index.md
|
|
@ -35,7 +35,7 @@ Docker Trusted Registry is perfect for:
|
|||
|
||||
Docker Trusted Registry is built on [version 2 of the Docker registry](https://github.com/docker/distribution).
|
||||
|
||||
To get your copy of Docker Trusted Registry, including a free trial, visit [the Docker Subscription page](https://hub-beta.docker.com/enterprise/). For more information on acquiring Docker Trusted Registry, see the [install page](/docker-trusted-registry/install/).
|
||||
To get your copy of Docker Trusted Registry, including a free trial, visit [the Docker Subscription page](https://hub.docker.com/enterprise/). For more information on acquiring Docker Trusted Registry, see the [install page](/docker-trusted-registry/install/).
|
||||
|
||||
> **Important**: Docker Trusted Registry must be used with the current version of the commercially
|
||||
> supported Docker Engine. You must install this version of Docker before
|
||||
|
|
|
|||
|
|
@ -1,106 +0,0 @@
|
|||
+++
|
||||
title = "Manually Install the CS Docker Engine"
|
||||
description = "Install instructions for the commercially supported Docker Engine"
|
||||
keywords = ["docker, documentation, about, technology, enterprise, hub, commercially supported Docker Engine, CS engine, registry"]
|
||||
[menu.main]
|
||||
parent="smn_dhe_install"
|
||||
+++
|
||||
|
||||
|
||||
# Manually Install the CS Docker Engine
|
||||
|
||||
You must first install the latest version of the commercially supported Docker Engine (CS engine) before you install the latest version of Docker Trusted Registry. Do this with an RPM or DEB package which you access using a script downloaded from your
|
||||
[Docker Hub Licenses page](https://hub-beta.docker.com/account/licenses/).
|
||||
|
||||
If you have not already done so, make sure you have first read the [installation overview](index.md) for Trusted Registry.
|
||||
|
||||
## Download the installation script
|
||||
|
||||
1. To download the commercially supported Docker Engine Bash installation script,
|
||||
log in to the [Docker Hub](https://hub-beta.docker.com) with the user-name used to
|
||||
obtain your license.
|
||||
2. Once you're logged in, go to the
|
||||
[Licenses](https://hub-beta.docker.com/account/licenses/) page in your Hub account's Settings section. This is accessed through the gear icon located in the upper right of your page.
|
||||
3. Click the button at the top right of the Licenses page that corresponds to your intended host operating system. The Bash setup script
|
||||
downloads.
|
||||
4. Next, select your operating system and follow the applicable steps.
|
||||
|
||||
### Install CentOS 7.1 & RHEL 7.0/7.1
|
||||
|
||||
1. Copy the downloaded Bash setup script to your RHEL host.
|
||||
2. Run the following to install the engine and its dependencies.
|
||||
3. Start the Docker daemon.
|
||||
|
||||
The following example illustrates these steps.
|
||||
|
||||
```
|
||||
$ sudo yum update && sudo yum upgrade
|
||||
$ chmod 755 docker-cs-engine-rpm.sh
|
||||
$ sudo ./docker-cs-engine-rpm.sh
|
||||
$ sudo yum install docker-engine-cs
|
||||
$ sudo systemctl enable docker.service
|
||||
$ sudo systemctl start docker.service
|
||||
```
|
||||
|
||||
To make using Docker easier, you can get non-sudo access to the Docker
|
||||
socket by adding your user to the `docker` group.
|
||||
|
||||
(*Optional*) Log out and back in again as seen in the next example.
|
||||
|
||||
|
||||
```
|
||||
$ sudo usermod -a -G docker $USER
|
||||
$ exit
|
||||
```
|
||||
> **Notes**:
|
||||
> You may need to reboot your server to update its RHEL kernel.
|
||||
> CentOS 7.0 is not supported.
|
||||
|
||||
### Install Ubuntu 14.04 LTS
|
||||
|
||||
1. Copy the downloaded Bash setup script to your Ubuntu host.
|
||||
2. Run the following to install the engine and its dependencies.
|
||||
|
||||
The following example illustrates these steps.
|
||||
|
||||
```
|
||||
$ sudo apt-get update && sudo apt-get upgrade
|
||||
$ sudo apt-get install -y linux-image-extra-virtual
|
||||
$ sudo reboot
|
||||
$ chmod 755 docker-cs-engine-deb.sh
|
||||
$ sudo ./docker-cs-engine-deb.sh
|
||||
$ sudo apt-get install docker-engine-cs
|
||||
```
|
||||
|
||||
3. Confirm Docker is running with `sudo service docker start`.
|
||||
|
||||
To make using Docker easier, you can get non-sudo access to the Docker socket by adding your user to the `docker` group.
|
||||
|
||||
4. (*Optional*) Log out and back in again as seen in the next example.
|
||||
|
||||
```
|
||||
$ sudo usermod -a -G docker $USER
|
||||
$ exit
|
||||
```
|
||||
|
||||
> **Note**: You may need to reboot your server to update its LTS kernel.
|
||||
|
||||
## Next step
|
||||
Your ready to install [Docker Trusted Registry]({{< relref "install.md" >}}).
|
||||
|
||||
## See also
|
||||
|
||||
* If you were manually installing Docker Trusted Registry, then continue with [those steps]({{< relref "install.md" >}}).
|
||||
* To configure for your environment, see the
|
||||
[Configuration instructions]({{< relref "configuration.md" >}}).
|
||||
* To use Docker Trusted Registry, see the [User guide]({{< relref "userguide.md" >}}).
|
||||
* To make administrative changes, see the [Admin guide]({{< relref "adminguide.md" >}}).
|
||||
* To see previous changes, see the [release notes]({{< relref "release-notes.md" >}}).
|
||||
|
||||
## See also
|
||||
|
||||
* To configure for your environment, see
|
||||
[Configuration instructions]({{< relref "configuration.md" >}}).
|
||||
* To use Docker Trusted Registry, see [the User guide]({{< relref "userguide.md" >}}).
|
||||
* To make administrative changes, see [the Admin guide]({{< relref "adminguide.md" >}}).
|
||||
* To see previous changes, see [the release notes]({{< relref "release-notes.md" >}}).
|
||||
|
|
@ -80,7 +80,7 @@ The following steps walk you through the 1-Click Launch settings:
|
|||
|
||||
5. From the Security Group box, select "Create new based on seller settings".
|
||||
|
||||
|
||||
|
||||
|
||||
This option has security implications. It allows incoming connections to the listed ports from any host or IP address. You should lock this down in line with your existing AWS security policies.
|
||||
|
||||
|
|
@ -136,7 +136,7 @@ interface:
|
|||
|
||||
You'll find the Instance ID on the "Description" tab on the EC2 Dashboard as shown in the image below:
|
||||
|
||||
|
||||
|
||||
|
||||
## Configure the Docker Trusted Registry Service
|
||||
|
||||
|
|
@ -15,7 +15,7 @@ The Trusted Registry installation includes a single instance of the commercially
|
|||
supported Docker Engine.
|
||||
|
||||
You can install additional instances of the commercially supported Docker Engine
|
||||
either on premise or through AWS. For more inforamtion, see the [installation
|
||||
either on premise or through AWS. For more information, see the [installation
|
||||
overview](index.md) for Trusted Registry.
|
||||
|
||||
The remainder of this document refers to the running instance of this AMI as a “Trusted Registry”.
|
||||
|
|
@ -93,7 +93,7 @@ The following steps walk you through the 1-Click Launch settings:
|
|||
|
||||
4. From the Security Group box, select "Create new based on seller settings".
|
||||
|
||||
|
||||
|
||||
|
||||
This option has security implications. It allows incoming connections to the listed ports from any host or IP address. You should lock this down in line with your existing AWS security policies..
|
||||
|
||||
|
|
@ -149,7 +149,7 @@ interface:
|
|||
|
||||
You'll find the Instance ID on the "Description" tab on the EC2 Dashboard as shown in the image below:
|
||||
|
||||
|
||||
|
||||
|
||||
## Configure the Docker Trusted Registry Service
|
||||
|
||||
|
|
@ -169,7 +169,7 @@ When you first login to the DTR Administration web interface you are prompted to
|
|||
|
||||
Your Docker Trusted Registry license file is available from Docker Hub. To download it, login to Docker Hub and click your username in the top right corner. Choose "Settings" and select the "Licenses" tab. Click the download button beneath your license.
|
||||
|
||||
|
||||
|
||||
|
||||
From the Docker Trusted Registry Administration web interface, select "Settings" and then "License". Under the "Apply a new license" heading select "Choose File". Select your downloaded license file and click "Save and restart".
|
||||
|
||||
|
|
|
|||
|
|
@ -87,7 +87,7 @@ The following steps walk you through the 1-Click Launch settings:
|
|||
|
||||
5. From the Security Group box, select "Create new based on seller settings".
|
||||
|
||||
|
||||
|
||||
|
||||
This option has security implications. It allows incoming connections to the listed ports from any host or IP address. You should lock this down in line with your existing AWS security policies.
|
||||
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 40 KiB |
|
Before Width: | Height: | Size: 168 KiB After Width: | Height: | Size: 168 KiB |
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
|
|
@ -1,5 +1,5 @@
|
|||
+++
|
||||
title = "Trusted Registry Installation Overview"
|
||||
title = "Trusted Registry installation overview"
|
||||
description = "Trusted Registry Installation Overview"
|
||||
keywords = ["docker, documentation, about, technology, install, enterprise, hub, CS engine, Docker Trusted Registry"]
|
||||
[menu.main]
|
||||
|
|
@ -8,58 +8,59 @@ identifier="smn_dhe_install"
|
|||
+++
|
||||
|
||||
# Trusted Registry Installation Overview
|
||||
Docker Trusted Registry is an enterprise grade on-premise registry bundled with commercially supported Docker Engines (CS Engine). This provides a base for you to build your Docker workflows.
|
||||
|
||||
Docker Trusted Registry is an enterprise-grade on-premise registry bundled with commercially supported Docker Engines (CS Engine). Use Docker Trusted Registry to manage your images, and the commercially supported Docker Engine to create, test, and share your application images. Together, these two Docker products can optimize your continuous integration (CI) and/or software deployment workflows.
|
||||
|
||||
Depending on your business requirements, there are two paths available for you to install Docker Trusted Registry (Trusted Registry). This document describes those options and prerequisites in order for you to make a decision that is best suited to your needs and provides the install directions for your selected path.
|
||||
|
||||
## Install Options
|
||||
## Install options
|
||||
|
||||
You can install Trusted Registry on premise or through any cloud provider. Installation through a cloud provider's marketplace is only supported on AWS and Microsoft Azure.
|
||||
You can install Trusted Registry on premise or through a cloud provider. Currently, Docker supports installation on any cloud provider.
|
||||
|
||||
## Get a license
|
||||
|
||||
Docker requires that you obtain a license to use the Trusted Registry. The installation path you choose affects the licensing methods available to you.
|
||||
Docker requires that you obtain a license to use the Trusted Registry. The installation path you choose (on premise or in the cloud) can affect the licensing methods available to you (bring your own license or cloud marketplace).
|
||||
|
||||
All installation paths support a license which you buy outright from Docker and
|
||||
apply during the installation process. If you would like, you can get a free
|
||||
trial license that is good for 30 days. To get a free trial or buy a
|
||||
license go to the [Subscription page](https://hub-beta.docker.com/enterprise/)
|
||||
license go to the [Subscription page](https://hub.docker.com/enterprise/)
|
||||
on Docker Hub.
|
||||
|
||||
If you are installing on AWS, you can use a license you bought direct using the Docker's Bring Your Own License (BYOL) AMI. You can also choose to pay by subscription installing with the AWS Business Day Support AMI. Under this model, your license is part of your Amazon Web Services (AWS) Business Support subscription.
|
||||
If you are installing on Microsoft Azure, you have the option of installing using the Virtual Hard Disk (VHD) in the Azure Marketplace. You should use a license you bought direct from Docker in this installation.
|
||||
|
||||
Buying a license is the only licensing option available with Microsoft Azure.
|
||||
If you are installing on AWS, you have the option of installing using Amazon Machine Images (AMI). You can use a license you bought direct using the Docker's Bring Your Own License (BYOL) AMI. You can also choose to pay-as-you-go by installing with the AWS Business Day Support (BDS) AMI. Under the BDS model, your license is part of your Amazon Web Services (AWS) Business Support subscription.
|
||||
|
||||
## Plan your install
|
||||
|
||||
The following steps are the general order of how you would obtain and install Docker Trusted Registry. You need to:
|
||||
This section summarizes the process of installing Docker Trusted Registry.
|
||||
|
||||
1. Get a license (either paid or trial) or managed through the pay as you go option.
|
||||
2. If installing on premise, install the commercially supported Engine for your production environment.
|
||||
3. Install Docker Trusted Registry on top of the commercially supported Engine.
|
||||
4. Apply the license (unless it is a part of your AWS subscription) and finish the install process.
|
||||
5. Configure your environment.
|
||||
6. Test your installation.
|
||||
7. (Optional) Install the CS Engine on another machine or configure existing CS engines. Again, you will have to configure and test.
|
||||
**(Option 1) Install on physical infrastructure or a cloud provider**
|
||||
* Obtain a trial or paid license.
|
||||
* Install the commercially supported Docker Engine.
|
||||
* Install the Trusted Registry.
|
||||
|
||||
You will want to configure a new CS Engine or existing Docker Engines to the Trusted Registry. Remember, your support is based on your type of license which is limited to the Trusted Registry and CS engines.
|
||||
**(Option 2) Install using AWS AMI**
|
||||
* Decide if you are going to bring your own license or use a subscription.
|
||||
* Depending on your choice:
|
||||
* Obtain a trial or paid license and install the bring your own license (BYOL) AMI.
|
||||
* Install the pay-as-you-go business day subscription (BDS) AMI.
|
||||
|
||||
Docker Trusted Registry requires that you use the latest version of the commercially supported Docker Engine. This means that when you upgrade, you will also be upgrading to the latest CS Engine. The instructions are the same, whether you plan to install for development or enterprise purposes. The difference between them is how extensive you choose to configure your environment.
|
||||
**After installing either option**
|
||||
|
||||
## Next steps
|
||||
* Start the DTR admin console.
|
||||
* If you have a license and not a subscription, install the license.
|
||||
* Configure your DTR installation.
|
||||
* Install additional CS engines on other systems.
|
||||
|
||||
Now that you have planned for your install, see the following documents:
|
||||
Remember, your support is based on your type of license. Each license has a single Trusted Registry and one or more CS engines. Your support for CS Engine installations is limited to the number of engines identified by your license.
|
||||
|
||||
* Get your [license]({{< relref "license.md" >}}).
|
||||
* Download the [commercially supported Docker Engine]({{< relref "csengineinstall.md" >}}).
|
||||
* Install by [bringing your own license (BYOL)]({{< relref "installAWS.md" >}}).
|
||||
* Install through the [pay as you go option]({{< relref "ami-launch.md" >}}).
|
||||
* Install [manually]({{< relref "install.md" >}}).
|
||||
Docker Trusted Registry requires that you use the latest version of the commercially supported Docker Engine. This means that when you upgrade Trusted Registry, you must also upgrade to the latest CS Engine.
|
||||
|
||||
## See also
|
||||
## Where to go next
|
||||
|
||||
* To configure for your environment, see the
|
||||
[configuration instructions]({{< relref "configuration.md" >}}).
|
||||
* To use Docker Trusted Registry, see the [User guide]({{< relref "userguide.md" >}}).
|
||||
* To make administrative changes, see the [Admin guide]({{< relref "adminguide.md" >}}).
|
||||
* To see previous changes, see the [release notes]({{< relref "release-notes.md" >}}).
|
||||
* If you are installing on physical infrastructure or a cloud provider, first install the [commercially supported Docker Engine](install-csengine.md) and then go on to install [Trusted Registry](install-dtry.md).
|
||||
|
||||
* If you are installing on AWS and would like to use a pre-built AMI and a license you purchased, see [bringing your own license (BYOL)](dtr-ami-byol-launch.md).
|
||||
|
||||
* If you are installing on AWS and would like to use the subscription license, see the [pay as you go BDS installation](dtr-ami-bds-launch.md).
|
||||
|
|
|
|||
|
|
@ -0,0 +1,140 @@
|
|||
+++
|
||||
title = "Manually Install the CS Docker Engine"
|
||||
description = "Install instructions for the commercially supported Docker Engine"
|
||||
keywords = ["docker, documentation, about, technology, enterprise, hub, commercially supported Docker Engine, CS engine, registry"]
|
||||
[menu.main]
|
||||
parent="smn_dhe_install"
|
||||
+++
|
||||
|
||||
|
||||
# Manually Install the CS Docker Engine
|
||||
|
||||
This document describes the process of obtaining and installing the Commercially
|
||||
Supported Docker Engine (CS Engine). Installing CS Engine is a prerequisite for
|
||||
installing the Docker Trusted Registry. You can use these instructions if you are installing CS Engine on physical or cloud infrastructure.
|
||||
|
||||
If your cloud provider is AWS, you have the option of installing CS Engine using an Amazon Machine Image (AMI) instead. For more information, read the [installation overview](index.md) to understand your options.
|
||||
|
||||
## Prerequisite
|
||||
|
||||
Installing CS Engine requires that you have a login to Docker Hub. If you have
|
||||
not already done so, go to Docker Hub and [sign up for an
|
||||
account](https://hub.docker.com).
|
||||
|
||||
Also, you must have a license for Docker Trusted Registry. This license allows
|
||||
you to run both Docker Trusted Registry and CS Engine. Before installing,
|
||||
[purchase a license or sign up for a free, 30 day trial license]((https://hub.docker.com/enterprise/)).
|
||||
|
||||
|
||||
## Install on CentOS 7.1 & RHEL 7.0/7.1
|
||||
|
||||
This section explains how to install on CentOS 7.1 & RHEL 7.0/7.1. Only these versions are supported. CentOS 7.0 is not supported. On RHEL, depending on your current level of updates, you may need to reboot your server to update its RHEL kernel.
|
||||
|
||||
1. Log into the system as a user with root or sudo permissions.
|
||||
|
||||
2. Update your `yum` repositories.
|
||||
|
||||
$ sudo yum update && sudo yum upgrade
|
||||
|
||||
3. In a browser, log in to the [Docker Hub](https://hub.docker.com) with the account you used to obtain your license.
|
||||
|
||||
4. Once you're logged in, go to your account's [Licenses](https://hub.docker.com/account/licenses/) page.
|
||||
|
||||
5. In the "Download and Install CS Engine" locate the script appropriate to your system.
|
||||
|
||||
6. Copy the script, paste it into your terminal, and press Return.
|
||||
|
||||
$ curl -s
|
||||
https://packagecloud.io/install/repositories/Docker/cs-public/script.rpm.sh |
|
||||
sudo bash sudo yum install docker-engine-cs
|
||||
|
||||
7. After the command completes, install the CS Engine with the following command:
|
||||
|
||||
$ sudo yum install docker-engine-cs
|
||||
|
||||
8. Enable the Docker daemon as a service and then start it.
|
||||
|
||||
$ sudo systemctl enable docker.service
|
||||
$ sudo systemctl start docker.service
|
||||
|
||||
9. Verify the installation was successful by running a simple container.
|
||||
|
||||
$ sudo docker run hello-world
|
||||
Unable to find image 'hello-world:latest' locally
|
||||
latest: Pulling from hello-world
|
||||
b901d36b6f2fd75: Pull complete
|
||||
0a6ba66e537a53a: Pull complete
|
||||
hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
|
||||
Digest: sha256:517f03be3f8169d84711c9ffb2b3235a4d27c1eb4ad147f6248c8040adb93113
|
||||
Status: Downloaded newer image for hello-world:latest
|
||||
|
||||
Hello from Docker.
|
||||
This message shows that your installation appears to be working correctly.
|
||||
|
||||
To generate this message, Docker took the following steps:
|
||||
1. The Docker client contacted the Docker daemon.
|
||||
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
|
||||
3. The Docker daemon created a new container from that image which runs the
|
||||
executable that produces the output you are currently reading.
|
||||
4. The Docker daemon streamed that output to the Docker client, which sent it
|
||||
to your terminal.
|
||||
|
||||
To try something more ambitious, you can run an Ubuntu container with:
|
||||
$ docker run -it ubuntu bash
|
||||
|
||||
Share images, automate workflows, and more with a free Docker Hub account:
|
||||
https://hub.docker.com
|
||||
|
||||
For more examples and ideas, visit:
|
||||
https://docs.docker.com/userguide/
|
||||
|
||||
10. Optionally, add non-sudo access to the Docker socket by adding your user to the `docker` group.
|
||||
|
||||
$ sudo usermod -a -G docker $USER
|
||||
|
||||
Log out and log back in to have your new permissions take effect.
|
||||
|
||||
|
||||
|
||||
## Install on Ubuntu 14.04 LTS
|
||||
|
||||
1. Log into the system as a user with root or sudo permissions.
|
||||
|
||||
2. Update your `yum` repositories.
|
||||
|
||||
$ sudo apt-get update && sudo apt-get upgrade
|
||||
|
||||
3. Install additional virtual drivers not in the base image.
|
||||
|
||||
$ sudo apt-get install -y linux-image-extra-virtual
|
||||
|
||||
You may need to reboot your server to after updating the LTS kernel.
|
||||
|
||||
4. In a browser, log in to the [Docker Hub](https://hub.docker.com) with the account you used to obtain your license.
|
||||
|
||||
5. Once you're logged in, go to your account's [Licenses](https://hub.docker.com/account/licenses/) page.
|
||||
|
||||
6. In the "Download and Install CS Engine" locate the script appropriate to your system.
|
||||
|
||||
7. Copy the script, paste it into your terminal, and press Return.
|
||||
|
||||
$ curl -s
|
||||
https://packagecloud.io/install/repositories/Docker/cs-public/script.deb.sh | sudo bash sudo apt-get install docker-engine-cs
|
||||
|
||||
8. Run the following to install commercially supported Docker Engine and its dependencies:
|
||||
|
||||
$ sudo apt-get install docker-engine-cs
|
||||
|
||||
9. Confirm the Docker daemon is running with `sudo service docker start`.
|
||||
|
||||
$ sudo service docker start
|
||||
|
||||
10. Optionally, add non-sudo access to the Docker socket by adding your user to the `docker` group.
|
||||
|
||||
$ sudo usermod -a -G docker $USER
|
||||
|
||||
Log out and log back in to have your new permissions take effect.
|
||||
|
||||
|
||||
## Next step
|
||||
You are ready to install [Docker Trusted Registry](install-dtry.md).
|
||||
|
|
@ -0,0 +1,188 @@
|
|||
+++
|
||||
title = "Manually install Trusted Registry"
|
||||
description = "Manually install Trusted Registry"
|
||||
keywords = ["docker, documentation, about, technology, understanding, enterprise, hub, registry"]
|
||||
[menu.main]
|
||||
parent="smn_dhe_install"
|
||||
+++
|
||||
|
||||
|
||||
# Manually install Trusted Registry
|
||||
|
||||
This document describes the process of obtaining, installing, and securing
|
||||
Docker Trusted Registry. You can use these instructions if you are installing Trusted Registry on a physical or cloud infrastructure.
|
||||
|
||||
If your cloud provider is AWS, you have the option of installing Trusted Registry using an Amazon Machine Image (AMI) instead. For more information, read the [installation overview](index.md) to understand your options.
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Docker Trusted Registry runs on the following 64-bit platforms:
|
||||
|
||||
* Ubuntu 14.04 LTS
|
||||
* RHEL 7.0 and 7.1
|
||||
* CentOS 7.1
|
||||
|
||||
Docker Trusted Registry requires the latest commercially supported Docker Engine (CS Engine), running on a supported host.
|
||||
|
||||
The Docker daemon listens to the Unix socket (the default) so that it can be
|
||||
bind-mounted into the Trusted Registry management containers. This allows
|
||||
Trusted Registry to manage itself and its updates. For this reason, the host you
|
||||
install on needs internet connectivity so it can access the updates.
|
||||
Additionally, your host needs to have TCP ports `80` and `443` available for the
|
||||
Docker Trusted Registry container port mapping.
|
||||
|
||||
Installing Trusted Registry requires that you have a login to Docker Hub (or the
|
||||
user-name of an administrator of the Hub organization that obtained an
|
||||
Enterprise license. If you already installed CS Engine, you should already have a [Hub account](https://hub.docker.com).
|
||||
|
||||
Also, you must have a license for Docker Trusted Registry. This license allows
|
||||
you to run both Docker Trusted Registry and CS Engine. Before installing,
|
||||
[purchase a license or sign up for a free, 30 day trial license]((https://hub.docker.com/enterprise/)).
|
||||
|
||||
|
||||
## Install Docker Trusted Registry
|
||||
|
||||
Trusted Registry is a self-installing application built and distributed using
|
||||
Docker and the [Docker Hub](https://hub.docker.com/). You install Docker Trusted
|
||||
Registry by running the "docker/trusted-registry" container. Once installed, it
|
||||
is able to restart and reconfigure itself using the Docker socket that is
|
||||
bind-mounted to this container.
|
||||
|
||||
1. Log in to the machine where you want to install Trusted Registry.
|
||||
|
||||
2. Verify that CS Engine is installed.
|
||||
|
||||
$ docker --version
|
||||
|
||||
> **Note:** To remain compliant with your Docker Trusted Registry support agreement, you **must** use the current version of commercially supported Docker Engine. Running the open source version of Engine is **not** supported.
|
||||
|
||||
3. Login into the Docker Hub from the command line.
|
||||
|
||||
$ docker login
|
||||
|
||||
4. Install the Trusted Registry
|
||||
|
||||
$ sudo bash -c "$(sudo docker run docker/trusted-registry install)"
|
||||
|
||||
> **Note**: `sudo` is needed for `docker/trusted-registry` commands to
|
||||
> ensure that the Bash script is run with full access to the Docker host.
|
||||
|
||||
The command executes a shell script that creates the needed directories,
|
||||
pulls the registry's images, and run its containers. Depending on your
|
||||
internet connection, this process may take several minutes to complete. A successful outcome completes as follows:
|
||||
|
||||
$ sudo bash -c "$(sudo docker run docker/trusted-registry install)"
|
||||
Unable to find image 'docker/trusted-registry:latest' locally
|
||||
Pulling repository docker/trusted-registry
|
||||
c46d58daad7d: Pulling image (latest) from docker/trusted-registry
|
||||
c46d58daad7d: Pulling image (latest) from docker/trusted-registry
|
||||
c46d58daad7d: Pulling dependent layers
|
||||
511136ea3c5a: Download complete
|
||||
fa4fd76b09ce: Pulling metadata
|
||||
fa4fd76b09ce: Pulling fs layer
|
||||
ff2996b1faed: Download complete
|
||||
...
|
||||
fd7612809d57: Pulling metadata
|
||||
fd7612809d57: Pulling fs layer
|
||||
fd7612809d57: Download complete
|
||||
Status: Downloaded newer image for docker/trusted-registry:latest
|
||||
Unable to find image 'docker/trusted-registry:1.1.0' locally
|
||||
Pulling repository docker/trusted-registry
|
||||
c46d58daad7d: Download complete
|
||||
511136ea3c5a: Download complete
|
||||
...
|
||||
Status: Image is up to date for docker/trusted-registry:1.1.0
|
||||
INFO [1.0.0_8ce62a61e058] Attempting to connect to docker engine dockerHost="unix:///var/run/docker.sock"
|
||||
INFO [1.0.0_8ce62a61e058] Running install command
|
||||
<...output truncated...>
|
||||
Creating container docker_trusted_registry_load_balancer with docker daemon unix:///var/run/docker.sock
|
||||
Starting container docker_trusted_registry_load_balancer with docker daemon unix:///var/run/docker.sock
|
||||
Bringing up docker_trusted_registry_log_aggregator.
|
||||
Creating container docker_trusted_registry_log_aggregator with docker daemon unix:///var/run/docker.sock
|
||||
Starting container docker_trusted_registry_log_aggregator with docker daemon unix:///var/run/docker.sock
|
||||
|
||||
5. Use `docker ps` to list all the running containers.
|
||||
|
||||
The listing should show the following were started:
|
||||
|
||||
* `docker_trusted_registry_load_balancer`
|
||||
* `docker_trusted_registry_image_storage_0`
|
||||
* `docker_trusted_registry_image_storage_1`
|
||||
* `docker_trusted_registry_admin_server`
|
||||
* `docker_trusted_registry_log_aggregator`
|
||||
* `docker_trusted_registry_auth_server`
|
||||
* `docker_trusted_registry_postgres`
|
||||
|
||||
6. Enter the `https://<host-ip>/`` your browser;s address bar to run the Trusted Registry interface.
|
||||
|
||||
Your browser warns you that this is an unsafe site, with a self-signed,
|
||||
untrusted certificate. This is normal and expected; allow this connection
|
||||
temporarily.
|
||||
|
||||
|
||||
## Set the Trusted Registry domain name
|
||||
|
||||
The Docker Trusted Registry Administrator site will also warn that the "Domain Name" is not set.
|
||||
|
||||
1. Select "Settings" from the global nav bar at the top of the page, and then set the "Domain Name" to the full host-name of your Docker Trusted Registry server.
|
||||
|
||||
2. Click the "Save and Restart Docker Trusted Registry Server" button to generate a new certificate, which will be used
|
||||
by both the Docker Trusted Registry Administrator web interface and the Docker Trusted Registry server.
|
||||
|
||||
3. After the server restarts, you will again need to allow the connection to the untrusted Docker Trusted Registry web admin site.
|
||||
|
||||
4. You see a warning notification that this instance of Docker Trusted Registry is unlicensed. You'll correct this in the next section.
|
||||
|
||||
## Apply your license
|
||||
|
||||
The Docker Trusted Registry services will not start until you apply your license.
|
||||
To do that, you'll first download your license from the Docker Hub and then
|
||||
upload it to your Docker Trusted Registry web admin server. Follow these steps:
|
||||
|
||||
1. If needed, log back into the [Docker Hub](https://hub.docker.com)
|
||||
using the user-name you used when obtaining your license. Under your name, go to Settings to display the Account Settings page. Click the Licenses submenu to display the Licenses page.
|
||||
|
||||
2. There is a list of available licenses. Click the download button to
|
||||
obtain the license file you want.
|
||||
|
||||
3. Go to your Docker Trusted Registry instance in your browser, click Settings in the global nav bar. Click License in the Settings nav bar. Click the Choose File button. It opens a standard file browser. Locate and select the license file you downloaded in the previous step. Approve the selection to close the dialog.
|
||||
|
||||
4. Click the Save and restart button. Docker Trusted Registry quits and then restarts with the applied the license.
|
||||
|
||||
5. Verify the acceptance of the license by confirming that the "Unlicensed copy"
|
||||
warning is no longer present.
|
||||
|
||||
## Secure the Trusted Registry
|
||||
|
||||
Securing Docker Trusted Registry is **required**. You will not be able to push
|
||||
or pull from Docker Trusted Registry until you secure it.
|
||||
|
||||
There are several options and methods for securing Docker Trusted Registry. For
|
||||
more information, see the [configuration documentation]({{< relref
|
||||
"configuration.md#security" >}})
|
||||
|
||||
## Push and pull images
|
||||
|
||||
Now that you have Docker Trusted Registry configured with a "Domain Name" and
|
||||
have your client Docker daemons configured with the required security settings,
|
||||
you can test your setup by following the instructions for [Using Docker Trusted
|
||||
Registry to Push and pull images]({{< relref "userguide.md" >}}).
|
||||
|
||||
## Docker Trusted Registry web interface and registry authentication
|
||||
|
||||
By default, there is no authentication set on either the Docker Trusted Registry
|
||||
web admin interface or the Docker Trusted Registry. You can restrict access
|
||||
using an in-Docker Trusted Registry configured set of users (and passwords), or
|
||||
you can configure Docker Trusted Registry to use LDAP- based authentication.
|
||||
|
||||
See [Docker Trusted Registry Authentication settings]({{< relref
|
||||
"configuration.md#authentication" >}}) for more details.
|
||||
|
||||
## See also
|
||||
|
||||
* To configure for your environment, see the
|
||||
[configuration instructions]({{< relref "configuration.md" >}}).
|
||||
* To use Docker Trusted Registry, see [the User guide]({{< relref "userguide.md" >}}).
|
||||
* To make administrative changes, see [the Admin guide]({{< relref "adminguide.md" >}}).
|
||||
* To see previous changes, see [the release notes]({{< relref "release-notes.md" >}}).
|
||||
|
|
@ -1,269 +0,0 @@
|
|||
+++
|
||||
title = "Manually install Trusted Registry"
|
||||
description = "Manually install Trusted Registry"
|
||||
keywords = ["docker, documentation, about, technology, understanding, enterprise, hub, registry"]
|
||||
[menu.main]
|
||||
parent="smn_dhe_install"
|
||||
+++
|
||||
|
||||
|
||||
# Manually install Trusted Registry
|
||||
|
||||
This document describes the process of obtaining, installing, and securing
|
||||
Docker Trusted Registry. Trusted Registry is installed from Docker containers.
|
||||
If you have not already done so, make sure you have first read the [installation
|
||||
overview](index.md) for Trusted Registry.
|
||||
|
||||
In general, the steps for installing the Engine for AWS AMI (BDS) are:
|
||||
|
||||
1. Acquire a license by purchasing Docker Trusted Registry or signing up for a trial license.
|
||||
2. Install the commercially supported Docker Engine.
|
||||
3. Install Docker Trusted Registry.
|
||||
4. Apply your license to your Docker Trusted Registry instance.
|
||||
5. Configure your settings.
|
||||
|
||||
|
||||
## Overview
|
||||
Docker Trusted Registry runs on the following platforms:
|
||||
|
||||
* Ubuntu 14.04 LTS
|
||||
* RHEL 7.0 and 7.1
|
||||
* CentOS 7.1
|
||||
|
||||
Docker Trusted Registry requires the following:
|
||||
|
||||
* The latest commercially supported Docker Engine, running
|
||||
on a supported host.
|
||||
|
||||
> **Note:** In order to remain in compliance with your Docker Trusted Registry support agreement,
|
||||
> you **must** use the current version of commercially supported Docker Engine.
|
||||
> Running the open source version of Engine is **not** supported.
|
||||
|
||||
* The Docker daemon needs to be listening to the unix socket (the default) so
|
||||
that it can be bind-mounted into the Docker Trusted Registry management containers, allowing
|
||||
Docker Trusted Registry to manage itself and its updates. For this reason, your Docker Trusted Registry host will also
|
||||
need internet connectivity so it can access the updates.
|
||||
|
||||
* Your host needs to have TCP ports `80` and `443` available for the Docker Trusted Registry
|
||||
container port mapping.
|
||||
|
||||
* You need the Docker Hub user-name and password used when obtaining
|
||||
the Docker Trusted Registry license (or the user-name of an administrator of the Hub organization
|
||||
that obtained an Enterprise license).
|
||||
|
||||
## Get your license
|
||||
|
||||
To start, get your copy of Docker Trusted Registry, including a free trial, at the [Docker Subscription page](https://hub-beta.docker.com/enterprise/).
|
||||
|
||||
Go to the license [documentation]({{< relref "license.md" >}}) to read about how to download the license. When you're finished, continue to the next step.
|
||||
|
||||
### Install the commercially supported Docker Engine
|
||||
|
||||
You download and save the CS engine install script from the Licenses page. Follow these [cs engine install ]({{< relref "csengineinstall.md" >}}) directions and then return to this document to continue the install.
|
||||
|
||||
#### CentOS 7.1 & RHEL 7.0/7.1 installation
|
||||
|
||||
1. Copy the downloaded Bash setup script to your RHEL host.
|
||||
2. Run the following to install commercially supported Docker Engine and its dependencies.
|
||||
3. Start the Docker daemon:
|
||||
|
||||
```
|
||||
$ sudo yum update && sudo yum upgrade
|
||||
$ chmod 755 docker-cs-engine-rpm.sh
|
||||
$ sudo bash ./docker-cs-engine-rpm.sh
|
||||
$ sudo yum install docker-engine-cs
|
||||
$ sudo systemctl enable docker.service
|
||||
$ sudo systemctl start docker.service
|
||||
```
|
||||
|
||||
In order to simplify using Docker, you can get non-sudo access to the Docker
|
||||
socket by adding your user to the `docker` group, then logging out and back in
|
||||
again:
|
||||
|
||||
```
|
||||
$ sudo usermod -a -G docker $USER
|
||||
$ exit
|
||||
```
|
||||
|
||||
> **Notes**:
|
||||
> * You may need to reboot your server to update its RHEL kernel.
|
||||
> * CentOS 7.0 is not supported.
|
||||
|
||||
|
||||
#### Ubuntu 14.04 LTS installation
|
||||
|
||||
1. Copy the downloaded Bash setup script to your Ubuntu host.
|
||||
2. Run the following to install commercially supported Docker Engine and its dependencies:
|
||||
|
||||
|
||||
$ sudo apt-get update && sudo apt-get upgrade
|
||||
$ sudo apt-get install -y linux-image-extra-virtual
|
||||
$ sudo reboot
|
||||
$ chmod 755 docker-cs-engine-deb.sh
|
||||
$ sudo ./docker-cs-engine-deb.sh
|
||||
$ sudo apt-get install docker-engine-cs
|
||||
|
||||
3. Confirm Docker is running with `sudo service docker start`.
|
||||
|
||||
4. (Optional) In order to simplify using Docker, get non-sudo access to the Docker socket by adding your user to the `docker` group, then logging out and back in again:
|
||||
|
||||
```
|
||||
$ sudo usermod -a -G docker $USER
|
||||
$ exit
|
||||
```
|
||||
|
||||
> **Note**: you may need to reboot your server to update its LTS kernel.
|
||||
|
||||
|
||||
## Install Docker Trusted Registry
|
||||
|
||||
Once the commercially supported Docker Engine is installed, you can install Docker Trusted Registry
|
||||
itself. Docker Trusted Registry is a self-installing application built and distributed using Docker
|
||||
and the [Docker Hub](https://hub-beta.docker.com/). It is able to restart
|
||||
and reconfigure itself using the Docker socket that is bind-mounted to its
|
||||
container.
|
||||
|
||||
Install Docker Trusted Registry by running the "docker/trusted-registry" container:
|
||||
|
||||
```
|
||||
$ sudo bash -c "$(sudo docker run docker/trusted-registry install)"
|
||||
```
|
||||
|
||||
> **Note**: `sudo` is needed for `docker/trusted-registry` commands to
|
||||
> ensure that the Bash script is run with full access to the Docker host.
|
||||
|
||||
The command will execute a shell script that creates the needed
|
||||
directories and then runs Docker to pull Docker Trusted Registry's images and run its containers.
|
||||
|
||||
Depending on your internet connection, this process may take several minutes to
|
||||
complete.
|
||||
|
||||
A successful installation will pull a large number of Docker images and should
|
||||
display output similar to:
|
||||
|
||||
```
|
||||
$ sudo bash -c "$(sudo docker run docker/trusted-registry install)"
|
||||
Unable to find image 'docker/trusted-registry:latest' locally
|
||||
Pulling repository docker/trusted-registry
|
||||
c46d58daad7d: Pulling image (latest) from docker/trusted-registry
|
||||
c46d58daad7d: Pulling image (latest) from docker/trusted-registry
|
||||
c46d58daad7d: Pulling dependent layers
|
||||
511136ea3c5a: Download complete
|
||||
fa4fd76b09ce: Pulling metadata
|
||||
fa4fd76b09ce: Pulling fs layer
|
||||
ff2996b1faed: Download complete
|
||||
...
|
||||
fd7612809d57: Pulling metadata
|
||||
fd7612809d57: Pulling fs layer
|
||||
fd7612809d57: Download complete
|
||||
c46d58daad7d: Pulling metadata
|
||||
c46d58daad7d: Pulling fs layer
|
||||
c46d58daad7d: Download complete
|
||||
c46d58daad7d: Download complete
|
||||
Status: Downloaded newer image for docker/trusted-registry:latest
|
||||
Unable to find image 'docker/trusted-registry:1.1.0' locally
|
||||
Pulling repository docker/trusted-registry
|
||||
c46d58daad7d: Download complete
|
||||
511136ea3c5a: Download complete
|
||||
fa4fd76b09ce: Download complete
|
||||
1c8294cc5160: Download complete
|
||||
117ee323aaa9: Download complete
|
||||
2d24f826cb16: Download complete
|
||||
33bfc1956932: Download complete
|
||||
48f0dd6c9414: Download complete
|
||||
65c30f72ecb2: Download complete
|
||||
d4b29764d0d3: Download complete
|
||||
5654f4fe5384: Download complete
|
||||
9b9faa6ecd11: Download complete
|
||||
0c275f56ca5c: Download complete
|
||||
ff2996b1faed: Download complete
|
||||
fd7612809d57: Download complete
|
||||
Status: Image is up to date for docker/trusted-registry:1.1.0
|
||||
INFO [1.0.0_8ce62a61e058] Attempting to connect to docker engine dockerHost="unix:///var/run/docker.sock"
|
||||
INFO [1.0.0_8ce62a61e058] Running install command
|
||||
<...output truncated...>
|
||||
Creating container docker_trusted_registry_load_balancer with docker daemon unix:///var/run/docker.sock
|
||||
Starting container docker_trusted_registry_load_balancer with docker daemon unix:///var/run/docker.sock
|
||||
Bringing up docker_trusted_registry_log_aggregator.
|
||||
Creating container docker_trusted_registry_log_aggregator with docker daemon unix:///var/run/docker.sock
|
||||
Starting container docker_trusted_registry_log_aggregator with docker daemon unix:///var/run/docker.sock
|
||||
$ docker ps
|
||||
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
|
||||
963ec2a4b047 docker/trusted-registry-nginx:1.1.0 "nginxWatcher" 5 minutes ago Up 5 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp docker_trusted_registry_load_balancer
|
||||
7eade5529049 docker/trusted-registry-distribution:v2.0.1 "registry /config/st 5 minutes ago Up 5 minutes 5000/tcp docker_trusted_registry_image_storage_0
|
||||
b968a8a986f9 docker/trusted-registry-distribution:v2.0.1 "registry /config/st 5 minutes ago Up 5 minutes 5000/tcp docker_trusted_registry_image_storage_1
|
||||
390d9d68a33a docker/trusted-registry-admin-server:1.1.0 "server" 5 minutes ago Up 5 minutes 80/tcp docker_trusted_registry_admin_server
|
||||
3f8a53dc5f35 docker/trusted-registry-log-aggregator:1.1.0 "log-aggregator" 5 minutes ago Up 5 minutes docker_trusted_registry_log_aggregator
|
||||
44083421fa16 docker/trusted-registry-garant:1.1.0 "garant /config/gara 5 minutes ago Up 5 minutes docker_trusted_registry_auth_server
|
||||
c4102adf73dc postgres:9.4.1 "/docker-entrypoint. 5 minutes ago Up 5 minutes 5432/tcp docker_trusted_registry_postgres
|
||||
```
|
||||
|
||||
Once this process completes, you can manage and configure your Docker Trusted Registry instance by pointing your browser to `https://<host-ip>/`.
|
||||
|
||||
Your browser warns you that this is an unsafe site, with a self-signed,
|
||||
untrusted certificate. This is normal and expected; allow this connection
|
||||
temporarily.
|
||||
|
||||
### Setting the Docker Trusted Registry Domain Name
|
||||
|
||||
The Docker Trusted Registry Administrator site will also warn that the "Domain Name" is not set.
|
||||
|
||||
1. Select "Settings" from the global nav bar at the top of the page, and then set the "Domain Name" to the full host-name of your Docker Trusted Registry server.
|
||||
|
||||
2. Click the "Save and Restart Docker Trusted Registry Server" button to generate a new certificate, which will be used
|
||||
by both the Docker Trusted Registry Administrator web interface and the Docker Trusted Registry server.
|
||||
|
||||
3. After the server restarts, you will again need to allow the connection to the untrusted Docker Trusted Registry web admin site.
|
||||
|
||||
4. You see a warning notification that this instance of Docker Trusted Registry is unlicensed. You'll correct this in the next section.
|
||||
|
||||
### Apply your license
|
||||
|
||||
The Docker Trusted Registry services will not start until you apply your license.
|
||||
To do that, you'll first download your license from the Docker Hub and then
|
||||
upload it to your Docker Trusted Registry web admin server. Follow these steps:
|
||||
|
||||
1. If needed, log back into the [Docker Hub](https://hub.docker.com)
|
||||
using the user-name you used when obtaining your license. Under your name, go to Settings to display the Account Settings page. Click the Licenses submenu to display the Licenses page.
|
||||
|
||||
2. There is a list of available licenses. Click the download button to
|
||||
obtain the license file you want.
|
||||
|
||||
3. Go to your Docker Trusted Registry instance in your browser, click Settings in the global nav bar. Click License in the Settings nav bar. Click the Choose File button. It opens a standard file browser. Locate and select the license file you downloaded in the previous step. Approve the selection to close the dialog.
|
||||
|
||||
4. Click the Save and restart button. Docker Trusted Registry quits and then restarts with the applied the license.
|
||||
|
||||
5. Verify the acceptance of the license by confirming that the "Unlicensed copy"
|
||||
warning is no longer present.
|
||||
|
||||
### Securing Docker Trusted Registry
|
||||
|
||||
Securing Docker Trusted Registry is **required**. You will not be able to push or pull from Docker Trusted Registry until you secure it.
|
||||
|
||||
There are several options and methods for securing Docker Trusted Registry. For more information,
|
||||
see the [configuration documentation]({{< relref "configuration.md#security" >}})
|
||||
|
||||
### Using Docker Trusted Registry to push and pull images
|
||||
|
||||
Now that you have Docker Trusted Registry configured with a "Domain Name" and have your client
|
||||
Docker daemons configured with the required security settings, you can test your
|
||||
setup by following the instructions for
|
||||
[Using Docker Trusted Registry to Push and pull images]({{< relref "userguide.md" >}}).
|
||||
|
||||
### Docker Trusted Registry web interface and registry authentication
|
||||
|
||||
By default, there is no authentication set on either the Docker Trusted Registry web admin
|
||||
interface or the Docker Trusted Registry. You can restrict access using an in-Docker Trusted Registry
|
||||
configured set of users (and passwords), or you can configure Docker Trusted Registry to use LDAP-
|
||||
based authentication.
|
||||
|
||||
See [Docker Trusted Registry Authentication settings]({{< relref "configuration.md#authentication" >}}) for more
|
||||
details.
|
||||
|
||||
## See also
|
||||
|
||||
* To configure for your environment, see the
|
||||
[configuration instructions]({{< relref "configuration.md" >}}).
|
||||
* To use Docker Trusted Registry, see [the User guide]({{< relref "userguide.md" >}}).
|
||||
* To make administrative changes, see [the Admin guide]({{< relref "adminguide.md" >}}).
|
||||
* To see previous changes, see [the release notes]({{< relref "release-notes.md" >}}).
|
||||
|
|
@ -77,6 +77,6 @@ and then start the Trusted Registry again:
|
|||
* To configure for your environment, see the
|
||||
[configuration instructions]({{< relref "configuration.md" >}}).
|
||||
* To use Docker Trusted Registry, see [the User guide]({{< relref "userguide.md" >}}).
|
||||
* See [installing the CS engine]({{< relref "csengineinstall.md" >}}).
|
||||
* See [installing the CS engine](install-csengine.md).
|
||||
* To make administrative changes, see [the Admin guide]({{< relref "adminguide.md" >}}).
|
||||
* To see previous changes, see [the release notes]({{< relref "release-notes.md" >}}).
|
||||
|
|
|
|||
13
license.md
13
license.md
|
|
@ -11,20 +11,19 @@ weight=9
|
|||
|
||||
# Licensing
|
||||
|
||||
To run Docker Trusted Registry, you need a Docker license, obtained either by purchasing
|
||||
Docker Trusted Registry,acquiring a trial license, or through an AWS hourly subscription. The license is associated with your free Docker Hub account or Docker Hub organization. If you don't have an account,
|
||||
you can set one up, which can be done at the same time as your license
|
||||
request.
|
||||
To run Docker Trusted Registry, you need a Docker license, obtained either by
|
||||
purchasing Docker Trusted Registry, acquiring a trial license, or through an AWS
|
||||
hourly subscription. If you a purchase a license or you have a trial license, it is associated with your free Docker Hub account or Docker Hub organization.
|
||||
|
||||
## Get your Trusted Registry License
|
||||
|
||||
1. Go to the [Docker Subscription page](https://hub-beta.docker.com/enterprise/) and select an edition. After completing a brief registration process, follow the steps to acquire it.
|
||||
1. Go to the [Docker Subscription page](https://hub.docker.com/enterprise/) and select an edition. After completing a brief registration process, follow the steps to acquire it.
|
||||
|
||||
**Note**: You may need to disable any pop-up blocker installed on your browser in order to complete the download.
|
||||
|
||||
2. After acquiring your license, view or download it by logging in to
|
||||
Docker Hub, going to your account settings (gear icon at upper right), and
|
||||
selecting ["Licenses"](https://hub-beta.docker.com/account/licenses/) from the
|
||||
selecting ["Licenses"](https://hub.docker.com/account/licenses/) from the
|
||||
top nav bar. Download the license by clicking the cloud icon.
|
||||
|
||||
The Licenses page displays your currently available licenses and if you selected the trial license, it also keeps track of how many trial days are remaining.
|
||||
|
|
@ -34,4 +33,4 @@ When installing Docker Trusted Registry, you must first obtain your license, the
|
|||
**Note** The Licenses page is where you download the CS engine script by selecting the operating system it needs to run on.
|
||||
|
||||
## See also
|
||||
* For information on how to download the CS engine, see [Installing the CS engine]({{< relref "csengineinstall.md" >}}).
|
||||
* For information on how to download the CS engine, see [Installing the CS engine](install-csengine.md).
|
||||
|
|
|
|||
Loading…
Reference in New Issue