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

Initial commit for dtr-ami-launch.md and engine-ami-launch.md 

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

Initial commit of dtr-ami-byol-launch.md for Docker Subscription for AWS BYOL install guide

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

moved files from docs/csengine to docs/

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

Initial commit for dtr-ami-launch.md and engine-ami-launch.md

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

Initial commit of dtr-ami-byol-launch.md for Docker Subscription for AWS BYOL install guide

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

delete csengine directory and update AMI launch docs

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

Change image refs to /docs/assets. Update with Betty's suggestions

Signed-off-by: nigelpoulton <nigelpoulton@hotmail.com>

Initial commit for dtr-ami-launch.md and engine-ami-launch.md

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

Initial commit of dtr-ami-byol-launch.md for Docker Subscription for AWS BYOL install guide

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

moved files from docs/csengine to docs/

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

Initial commit for dtr-ami-launch.md and engine-ami-launch.md

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

Initial commit of dtr-ami-byol-launch.md for Docker Subscription for AWS BYOL install guide

Signed-off-by: Nigel <nigelpoulton@hotmail.com>

delete csengine directory and update AMI launch docs

Signed-off-by: Nigel <nigelpoulton@hotmail.com>
This commit is contained in:
Nigel 2015-09-21 21:01:21 +01:00 committed by nigelpoulton
parent ad707e0864
commit d9d1e0b0bb
7 changed files with 577 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
assets/aws-dtr-sg-rules.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 15 KiB

BIN
assets/aws-engine-sg-rules.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 40 KiB

BIN
assets/aws-instance-id.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 168 KiB

BIN
assets/dtr-license-download.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 21 KiB

173
dtr-ami-byol-launch.md Normal file
View File

@ -0,0 +1,173 @@
# Install Docker Subscription for AWS (BYOL)
This article walks you through the process of launching the *Docker Subscription for AWS (BYOL)* AMI as an EC2 instance in the Amazon Web Services (AWS) cloud.
The Docker Subscription for AWS (BYOL) AMI launches an instance of Docker Trusted Registry. The remainder of this document refers to the running instance of this AMI as a “Trusted Registry”.
> **Note:** Docker Trusted Registry is intended to be used in conjunction with the commercially supported Docker Engine. The commercially supported Docker Engine is available on AWS via the [*Docker Engine for AWS (Business Day Support AMI*)](https://aws.amazon.com/marketplace/pp/B014VG1R4Q/ref=srh_res_product_title?ie=UTF8&sr=0-5&qid=1442928397927.).
To learn more about *Docker Subscription for AWS* visit our [AWS Documentation](https://www.docker.com/aws).
## Prerequisites
You will need the following to complete this guide:
1. An AWS account with permissions to launch EC2 Instances.
2. A valid Docker Subscription license.
Contact your AWS administrator if your AWS account is provided by your company and you do not have permissions to launch EC2 Instances.
If you do not have a valid Docker Subscription license the following options are available:
- Use the *Docker Trusted Registry for AWS (Business Day Support)* AMI and the *Docker Engine for AWS (Business Day Support)* AMI, both of which include the cost of a Docker Subscription.
- Register for a [Free 30 Day Trial](https://hub.docker.com/enterprise/trial/).
- [Contact Docker](https://www.docker.com/contact) to obtain a quote for a Docker Subscription.
# Install procedure
These instructions show you how to locate, install, and launch a Trusted Registry using the *Docker Subscription for AWS (BYOL)* AMI from Amazon's AWS Marketplace.
The AWS Marketplace allows you to do a "1-Click Launch" or "Manual Launch".
The *Manual Launch* allows you to launch using the AWS EC2 Console. It allows for fine control of EC2 instance settings such as:
- Instance type
- VPC settings
- Storage
- Instance tags
- Security Group settings
The *1-Click Launch* is quicker, provides default values for most settings, and dynamically updates the Cost Estimator. This install shows you how to do a *1-Click Launch*. The entire process should take about 15 minutes to complete.
## Locate the Docker Trusted Registry AMI
1. If you haven't already done so, open your browser to the <a href="https://aws.amazon.com/marketplace">Amazon AWS Marketplace</a>.
2. Search the Marketplace for "Docker Subscription for AWS (BYOL)".
3. Select the "Docker Subscription for AWS (BYOL)" AMI from the list of results.
The Marketplace entry provides details on the product.
4. Press "Continue" to move to the launch step.
If you are not logged into AWS, the system prompts you to.
5. Enter your AWS login credentials.
When your login succeeds, the browser displays the "Launch on EC2" page.
6. Make sure that the "1-Click Launch" tab is selected.
## Deploy the 1-Click Launch
You can deploy a Trusted Registry instance to a private or public subnet. A private subnet provides added security but also prevents your Trusted Registry instance from being directly addressable on the internet. If you choose to deploy to a private subnet, you may need to access your Trusted Registry via a Bastion host or a management instance within your VPC.
These instructions launch a Trusted Registry on an EC2 instance in a public subnet with a public IP, so that gaining access to it in the "Connecting to the Docker Trusted Registry Administration web interface" section is simplified.
> **Note:** Deploying a Trusted Registry instance to an AWS Public Subnet will automatically assign it a Public IP and Public DNS. Do not forget that AWS Public IPs and Public DNS names change when an EC2 Instance is rebooted. If you want your Trusted Registry EC2 Instance to be directly accessible over the internet you should assign it an Elastic IP.
The following steps walk you through the 1-Click Launch settings:
1. Select the version you want to deploy from the list of available versions.
2. Select the Region you want to deploy to from the "Region" dropdown.
3. Select the EC2 Instance type
Be sure to check the "Pricing Details" and "Cost Estimator" boxes when changing EC2 Instance types.
3. Select the VPC and Subnet you want to deploy to from the "VPC" and "Subnet" dropdowns.
4. From the Security Group box, select "Create new based on seller settings".
![](../assets/aws-dtr-sg-rules.png)
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..
5. Select an existing or add a new key pair using the "Key Pair" box.
If you choose to use an existing key pair, be sure to choose one that you have access to, as this cannot be changed after the instance is launched.
6. Review your choices and check the values in the Cost Estimator.
Changing your selected Region and VPC settings can cause your selected EC2 Instance type to reset to the default value of "m3.2xlarge".
7. If you are happy with your configuration and estimated charges, click "Launch with 1-Click".
8. Go to the <a href="https://console.aws.amazon.com/ec2/v2/home">EC2 Dashboard</a> to view your instance.
## Connect to the Docker Trusted Registry Administration web interface
You administer your Trusted Registry server via the Administration web
interface (hereafter referred to as *DTR Administration web interface*).
You can configure your own custom DNS names for your EC2 instance
using CNAME records and so forth. Or, you can use the default DNS names provided by
AWS. These instructions use the default DNS name provided by AWS.
The DTR Administration web interface is exposed on port 443 (HTTPS) of
the EC2 instance. To connect to the DTR Administration web
interface:
1. Log into the AWS Console.
2. Go to the EC2 Dashboard.
3. Choose the "Running Instances" option.
4. Select the Trusted Registry EC2 instance.
5. Select the "Description" tab.
6. Locate the Public DNS or Public IP of the EC2 instance.
7. Copy the Public DNS or Public IP into your browser's address bar and press `return`.
> **Note:** Connecting to the DTR Administration web
interface may result in a certificate related browser warning. This is
expected behavior and you can bypass the warning.
The interface prompts you for the username and password.
8. Enter "admin" for the username.
9. For the password, use the EC2 Instance ID.
You'll find the Instance ID on the "Description" tab on the EC2 Dashboard as shown in the image below:
![](../assets/aws-instance-id.png)
## Configure the Docker Trusted Registry Service
When you first login to the DTR Administration web interface you are prompted to complete two configuration items:
1. Configure the "Domain name" on the "General" tab of the "Settings" page.
This should be a fully qualified domain name that you have configured for your Trusted Registry service.
Enter your desired domain name and click the "Save and restart" button at the bottom of the page.
After the Trusted Registry server restarts, return to the DTR Administration web interface. The browser displays another certificate related browser warning. Changing the Domain Name property of your Trusted Registry server generates a new self-signed certificate. Again, this is expected behavior and you can bypass the warning.
Log back in to the DTR Administration web interface.
2. License your copy of Docker Trusted Registry from the "License" tab of the "Settings" page.
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.
![](../assets/dtr-license-download.png)
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".
> **Note:** Restarting your Trusted Registry from the DTR Administration web interface, or as part of the above procedures, does not restart the EC2 instance. Therefore, the Public IP and Public DNS of the EC2 instance does not change.
Log into the DTR Administration web interface and change the default password for the "admin" account from the "Auth" tab on the "Settings" page.
Your Docker Trusted Registry server is now ready for use.
## Next Steps
For more information on using DTR, go to the
[User's Guide](https://docs.docker.com/docker-trusted-registry/userguide/).

143
dtr-ami-launch.md Normal file
View File

@ -0,0 +1,143 @@
# Install Docker Trusted Registry for AWS (Business Day Support)
This article walks you through the process of launching the *Docker Trusted Registry for AWS (Business Day Support)* AMI as an EC2 instance in the Amazon Web Services (AWS) cloud.
This AMI launches an instance of Docker Trusted Registry (DTR). The remainder of this document refers to the running instance of this AMI as a “Trusted Registry”. This AMI requires the use of Docker Engine for AWS (Business Day Support).
To learn more about *Docker Trusted Registry for AWS* visit our [AWS Documentation](https://www.docker.com/aws).
## Prerequisites
You can locate, install, and launch the AMI from the Amazon AWS Marketplace or with the AWS EC2 Console by selecting the AMI from the "Launch Instance" dialog. Both the AWS Marketplace and the AWS EC2 Console require that you have an AWS account to launch the AMI.
If your account is supplied through your company, your company's administrator must have given you permissions to launch EC2 instances. If you receive a permissions error when following these instructions, contact your AWS administrator for help.
# Install procedure
These instructions show you how to locate, install, and launch a Trusted Registry (DTR) from Amazon's AWS Marketplace. The AWS Marketplace allows you to do a "1-Click Launch" or "Manual Launch".
The *Manual Launch* allows you to launch using the AWS EC2 Console. It allows for fine control of EC2 instance settings such as:
- Instance type
- VPC settings
- Storage
- Instance tags
- Security Group settings
The *1-Click Launch* is quicker, provides default values for most settings, and dynamically updates the Cost Estimator. This install shows you how to do a *1-Click Launch*. The entire process should take about 15 minutes to complete.
## Locate the Docker Trusted Registry AMI
1. If you haven't already done so, open your browser to the <a href="https://aws.amazon.com/marketplace">Amazon AWS Marketplace</a>.
2. Search the Marketplace for "Docker Trusted Registry for AWS (Business Day Support)".
3. Select the "Docker Trusted Registry for AWS (Business Day Support)" AMI from the list of results.
The Marketplace entry provides details on the product.
4. Press "Continue" to move to the launch step.
If you are not logged into AWS, the system prompts you to.
5. Enter your AWS login credentials.
When your login succeeds, the browser displays the "Launch on EC2" page.
6. Make sure that the "1-Click Launch" tab is selected.
## Deploy the 1-Click Launch
You can deploy a Trusted Registry to a private or public subnet. A private subnet provides added security but also prevents your Trusted Registry instance from being directly addressable on the internet. If you choose to deploy to a private subnet, you may need to access your Trusted Registry via a Bastion host or a management instance within your VPC.
These instructions launch an EC2 instance into a public subnet with a public IP so that gaining access to it in the "Connecting to the Docker Trusted Registry Administration web interface" section is simplified.
> **Note:** Deploying a Trusted Registry instance to an AWS Public Subnet will automatically assign it a Public IP and Public DNS. Do not forget that AWS Public IPs and Public DNS names change when an EC2 Instance is rebooted. If you want your Trusted Registry EC2 Instance to be directly accessible over the internet you should assign it an Elastic IP.
The following steps walk you through the 1-Click Launch settings:
1. From the "Software Pricing" box, select a "Subscription Term" and an "Applicable Instance Type."
These two options contribute to the overall cost of running your choice of EC2 instance. The combination of these two fees make up the running costs of your EC2 instance, and are shown in the "Cost Estimator" box. Make sure you understand these costs before launching your instance.
2. Select the version you want to deploy from the list of available versions.
3. Select the Region you want to deploy to from the "Region" dropdown.
4. Select the VPC and Subnet you want to deploy to from the "VPC" and "Subnet" dropdowns.
5. From the Security Group box, select "Create new based on seller settings".
![](../assets/aws-dtr-sg-rules.png)
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.
6. Select an existing or add a new key pair using the "Key Pair" box.
If you choose to use an existing key pair, be sure to choose one that you have access to, as this cannot be changed after the instance is launched.
7. Review your choices and check the values in the Cost Estimator.
Changing your selected Region and VPC settings can cause your selected EC2 instance type to reset to the default value of "m3.2xlarge".
8. If you are happy with your configuration and estimated charges, click "Launch with 1-Click".
9. Go to the <a href="https://console.aws.amazon.com/ec2/v2/home">EC2 Dashboard</a> to view your instance.
## Connect to the Docker Trusted Registry Administration web interface
You administer your Trusted Registry server via the Administration web
interface. You can configure your own custom DNS names for your EC2 instance
using CNAME records and so forth. Or, you can use the default DNS names provided by
AWS. These instructions use the default DNS name provided by AWS.
The DTR Administration web interface is exposed on port 443 (HTTPS) of
the EC2 instance. To connect to the DTR Administration web
interface:
1. Log into the AWS Console.
2. Go to the EC2 Dashboard.
3. Choose the "Running Instances" option.
4. Select the Trusted Registry EC2 instance.
5. Select the "Description" tab.
6. Locate the Public DNS or Public IP of the EC2 instance.
7. Copy the Public DNS or Public IP into your browser's address bar and press `return`.
> **Note:** Connecting to the DTR Administration web
interface may result in a certificate related browser warning. This is
expected behavior and you can bypass the warning.
The interface prompts you for the username and password.
8. Enter "admin" for the username.
9. For the password, use the EC2 Instance ID.
You'll find the Instance ID on the "Description" tab on the EC2 Dashboard as shown in the image below:
![](../assets/aws-instance-id.png)
## Configure the Docker Trusted Registry Service
When you first login to the DTR Administration web interface you are prompted to configure the "Domain name" on the "General" tab of the "Settings" page. The Domain Name should be a fully qualified domain name that you have configured for your DTR service. Enter your desired domain name and click the "Save and restart" button at the bottom of the page.
After the DTR server restarts, return to the DTR Administration web interface. The browser displays another certificate related browser warning. Changing the Domain Name property of your DTR server generates a new self-signed certificate. Again, this is expected behavior and you can bypass the warning.
Log into the Trusted Registry and change the default password for the "admin" account from the "Auth" tab on the "Settings" page in the DTR Administration web interface.
Your Docker Trusted Registry server is now ready for use.
## Next Steps
For more information on using DTR, go to the
[User's Guide](https://docs.docker.com/docker-trusted-registry/userguide/).

261
engine-ami-launch.md Normal file
View File

@ -0,0 +1,261 @@
# Install Docker Engine for AWS (Business Day Support)
This article walks you through the following steps to launch the *Docker Engine for AWS (Business Day Support)* AMI as an EC2 instance in the Amazon Web Services (AWS) cloud:
1. Locate the *Docker Engine for AWS (Business Day Support)* AMI
2. Deploy with 1-Click Launch
3. Connect to the Docker Engine
4. Confirm the Docker Engine is running
5. Configure *Docker Engine for AWS* to use *Docker Trusted Registry for AWS*
6. Push a Docker image to your *Docker Trusted Registry for AWS*
The *Docker Engine for AWS (Business Day Support)* AMI launches an instance of the commercially supported Docker Engine. Upgrading the Docker Engine to a non commercially supported version is not supported. This AMI requires the use of Docker Trusted Registry for AWS (Business Day Support) to maintain a supported configuration.
To learn more about *Docker Engine for AWS* visit our [AWS Documentation](https://www.docker.com/aws).
## Prerequisites
You can locate, install, and launch the AMI from the Amazon AWS Marketplace, or with the AWS EC2 Console by selecting the AMI from the "Launch Instance" dialog. Both the AWS Marketplace and the AWS EC2 Console require that you have an AWS account to launch the AMI.
If your account is supplied through your company, your company's administrator must have given you permissions to launch EC2 instances. If you receive a permissions error when following these instructions, contact your AWS administrator for help.
# Install procedure
These instructions show you how to locate, install, and launch the Docker Engine from Amazon's AWS Marketplace. The AWS Marketplace allows you to do a "1-Click Launch" or "Manual Launch".
The *Manual Launch* allows you to launch using the AWS EC2 Console. It allows for fine control of EC2 instance settings such as:
- Instance type
- VPC settings
- Storage
- Instance tags
- Security Group settings
The *1-Click Launch* is quicker, provides default values for most settings, and dynamically updates the Cost Estimator. This install shows you how to do a *1-Click Launch*. The entire process should take about 20 minutes to complete.
## Locate the Docker Engine for AWS (Business Day Support) AMI
1. If you haven't already done so, open your browser to the <a href="https://aws.amazon.com/marketplace">Amazon Marketplace</a>.
2. Search the Marketplace for "Docker Engine for AWS (Business Day Support)".
3. Select the "Docker Engine for AWS (Business Day Support)" AMI from the list of results.
The Marketplace entry provides details on the product.
4. Press "Continue" to move to the launch step.
If you are not logged into AWS, the system prompts you to.
5. Enter your AWS login credentials.
When your login succeeds, the browser displays the "Launch on EC2" page.
6. Make sure that the "1-Click Launch" tab is selected.
## Deploy with 1-Click Launch
You can deploy the Docker Engine AMI to an Instance in a private or public subnet. A private subnet provides added security but also prevents your Docker Engine instance from being directly addressable on the internet. If you choose to deploy to a private subnet, you may need to access your Docker Engine instance via a Bastion host or a management instance within your VPC.
These instructions launch an EC2 instance into a public subnet with a public IP, so that gaining access to it in the "Connect to the Docker Engine" section is simplified.
The following steps walk you through the 1-Click Launch settings:
1. From the "Software Pricing" box, select a "Subscription Term" and an "Applicable Instance Type."
These two options contribute to the overall cost of running your choice of EC2 instance. The combination of these two fees make up the running costs of your EC2 instance, and are shown in the "Cost Estimator" box. Make sure you understand these costs before launching your instance.
2. Select the version you want to deploy from the list of available versions.
3. Select the Region you want to deploy to from the "Region" dropdown.
4. Select the VPC and Subnet you want to deploy to from the "VPC" and "Subnet" dropdowns.
5. From the Security Group box, select "Create new based on seller settings".
![](../assets/aws-engine-sg-rules.png)
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.
6. Select an existing or add a new key pair using the "Key Pair" box.
If you choose to use an existing key pair, be sure to choose one that you have access to, as this cannot be changed after the instance is launched.
7. Review your choices and check the values in the Cost Estimator.
Changing your selected Region and VPC settings can cause your selected EC2 instance type to reset to the default value of "m3.medium".
8. If you are happy with your configuration and estimated charges, click "Launch with 1-Click".
9. Go to the <a href="https://console.aws.amazon.com/ec2/v2/home">EC2 Dashboard</a> to view your instance.
## Connect to the Docker Engine
You administer your Docker Engine using the `docker` command line tool. You can run the `docker` command line tool directly from your Docker Engine EC2 Instance, or remotely from another machine with network connectivity to your Docker Engine EC2 Instance. These instructions administer the Docker Engine directly from the Docker Engine EC2 Instance.
To connect to the command line of your Docker Engine EC2 Instance:
1. Log into the AWS Console.
2. Go to the EC2 Dashboard.
3. Choose the "Running Instances" option.
4. Right-click your Docker Engine EC2 Instance and choose "Connect".
5. Copy and paste the "Example:" command into a terminal window.
6. Change the username from "root" to "ec2-user".
After changing the username from "root" to "ec2-user", the command should look like the following:
`$ ssh -i <key-pair> ec2-user@52.27.119.45`
The <key-pair> will reflect the name of the key pair you launched the instance with and the IP address will match the IP of your Docker Engine EC2 Instance.
7. Press `Return`.
Connecting to the Docker Engine EC2 Instance will gnerate and authentication warning. This is expected behavior and you can continue.
If you're connecting from a Windows machine, you'll need to have an SSH client isntalled and in your PATH variable.
For more information about connecting to your Docker Engine EC2 Instance over SSH, right-click your EC2 Instance and choose "Connect".
## Confirm the Docker Engine is ready to use
The Docker daemon is configured to automatically start with your Docker Engine EC2 Instance.
Run the [`docker version`](https://docs.docker.com/reference/commandline/version) command from the command line of your Docker Engine EC2 Instance:
$ sudo docker version
Client version: 1.6.2-cs5
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 9c454bd
OS/Arch (client): linux/amd64
Server version: 1.6.2-cs5
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 9c454bd
OS/Arch (server): linux/amd64
If you get a "FATA[0000]" error for the server portion of the output, make sure you are using `sudo` at the beginning of the command. If you are using `sudo` and still get the error, check the status of the Docker service with the `sudo service docker status` command, and try restarting the service with the `sudo service docker restart` command.
## Configuring the Docker Engine to use Docker Trusted Registry
This section of the guide walks you through the steps to configure *Docker Engine for AWS* to use *Docker Trusted Registry for AWS* as its image registry.
This guide assumes you have a working version of *Docker Trusted Registry for AWS* running in your AWS VPC at "ec2-52-24-229-123.us-west-2.compute.amazonaws.com". You will need to substitute this value with the correct value for your environment for the remainder of this guide.
For information on installing Docker Trusted Registry for AWS, see our [AWS Documentation](https://www.docker.com/aws).
> **Note:** Docker Trusted Registry is only supported with the commercially supported Docker Engine. For more information see the [online compatibility matrix](https://www.docker.com/compatibility-maintenance).
1. Save the Domain name of your Docker Trusted Registry for AWS service to an environment variable:
`$ export DOMAIN_NAME=ec2-52-24-229-123.us-west-2.compute.amazonaws.com`
Don't forget to substitute the Domain name in the command above with the correct domain name in your environment.
2. Retrieve the certificate from your Docker Trusted Registry server and store it locally on the Docker Engine for AWS EC2 Instance:
`$ sudo openssl s_client -connect $DOMAIN_NAME:443 -showcerts </dev/null 2>/dev/null | openssl x509 -outform PEM | sudo tee /usr/local/share/ca-certificates/$DOMAIN_NAME.crt`
3. Add the retrieved certificate as a trusted root:
`$ sudo update-ca-certificates`
4. Restart the Docker service:
`$ sudo service docker restart`
Your *Docker Engine for AWS* EC2 Instance is now configured to be able to push and pull images to your instance of *Docker Trusted Registry for AWS*.
## Push a Docker image to your Docker Trusted Registry for AWS
You push and pull images to Docker Trusted Registry using the normal [`docker push`](https://docs.docker.com/reference/commandline/push) and [`docker pull`](https://docs.docker.com/reference/commandline/pull) commands.
The following steps walk you through the process of pulling an image from Docker Hub, pushing that same image to your Docker Trusted Registry, and then pulling it back from your Docker Trusted Registry.
This guide assumes your Docker Trusted Registry is reachable at "ec2-52-24-229-123.us-west-2.compute.amazonaws.com". You will need to substitute this value with the DNS name of your own Docker Trusted Registry. All commands are ran from your *Docker Engine for AWS* EC2 Instance.
1. Pull a Docker image from Docker Hub with the [`docker pull`](https://docs.docker.com/reference/commandline/pull) command:
$ sudo docker pull busybox
latest: Pulling from busybox
cf2616975b4a: Pull complete
79722f6accc3: Pull complete
0f864637f229: Pull complete
busybox: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:c451012efb6e79b9cf93f48a326a195acfcdf01cadf4271d678d03e031c214d3
Status: Downloaded newer image for busybox:latest
2. Verify the image is stored locally with the [`docker images`](https://docs.docker.com/reference/commandline/images) command:
$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
busybox latest 0f864637f229 2 days ago 2.433 MB
3. Tag the image for storage in your Docker Trusted Registry using the [`docker tag`](https://docs.docker.com/reference/commandline/tag) command:
`$ sudo docker tag 0f864637f229 ec2-52-24-229-123.us-west-2.compute.amazonaws.com/devops/busybox:0.1`
This will tag the local busybox image (0f864637f229) so that it can be pushed to the "devops" repository in your Docker Trusted Registry at "ec2-52-24-229-123.us-west-2.compute.amazonaws.com". Don't forget to substitute the image ID (0f864637f229) and the domain anme of the Docker Trusted Registry with the appropriate values for your environment.
4. Log in to the Docker Trusted Registry with the [`docker login`](https://docs.docker.com/reference/commandline/login) command:
`$ sudo docker login ec2-52-24-229-123.us-west-2.compute.amazonaws.com`
By default, Docker Trusted Registry requires you to login before you can push and pull images. It is recommended that you create user accounts with the appropriate permissions on the "Settings" > "Auth" tab in the Docker Trusted Registry Administration web interface.
5. Push the local tagged BusyBox image to your Docker Trusted Registry with the [`docker push`](https://docs.docker.com/reference/commandline/push) command:
$ sudo docker push ec2-52-24-229-123.us-west-2.compute.amazonaws.com/devops/busybox
The push refers to a repository [ec2-52-24-229-123.us-west-2.compute.amazonaws.com/devops/busybox] (len: 1)
0f864637f229: Image already exists
79722f6accc3: Image successfully pushed
cf2616975b4a: Image successfully pushed
Digest: sha256:06a01d4fc44fd4d3fb9fbb808e337822b2af3a97ca1ffdde7c0548eae33d3fec
6. Delete the local copies of the "busybox" image from the Docker Engine EC2 Instance using the [`docker rmi`](https://docs.docker.com/reference/commandline/rmi) command:
`$ sudo docker rmi -f 0f864637f229`
You may need to run the command above command twice. The first time you run the command, it deletes the tagged image we created earlier with the `docker tag` command. The second time you run the command it deletes the image pulled from Docker Hub.
7. Verify there are no local copies of the "busybox" image:
$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
8. Pull a copy of the busybox image from your Docker Trusted Registry:
$ sudo docker pull ec2-52-24-229-123.us-west-2.compute.amazonaws.com/devops/busybox:0.1
0.1: Pulling from ec2-52-24-229-123.us-west-2.compute.amazonaws.com/devops/busybox
cf2616975b4a: Pull complete
79722f6accc3: Pull complete
0f864637f229: Already exists
Digest: sha256:06a01d4fc44fd4d3fb9fbb808e337822b2af3a97ca1ffdde7c0548eae33d3fec
Status: Downloaded newer image for ec2-52-24-229-123.us-west-2.compute.amazonaws.com/devops/busybox:0.1
9. Verify that the image is now stored locally:
$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
ec2-52-24-229-123.us-west-2.compute.amazonaws.com/devops/busybox 0.1 0f864637f229 2 days ago 2.433 MB
You have now successfully deployed the *Docker Engine for AWS (Business Day Support)* AMI and configured it to work with *Docker Trusted Registry for AWS (Business Day Support)*.
## Next Steps
For more information on using Docker Enginer in AWS, visit our [AWS Documentation](https://www.docker.com/aws).