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

Merge pull request #619 from fredlf/edit-qsg 

Changes from re-validation of QSG for 1.3
This commit is contained in:
Sven Dowideit 2015-08-22 12:08:23 +10:00
parent 81321cd168 c8c18b5b42
commit 8b8a9f548a
1 changed files with 16 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
quick-start.md
View File

@ -11,7 +11,7 @@ weight=1
# Docker Trusted Registry Quick Start: Basic User Workflow # Docker Trusted Registry Quick Start Guide: Basic User Workflow
## Overview ## Overview
@ -64,19 +64,19 @@ command to pull the public Jenkins image.
$ docker pull jenkins $ docker pull jenkins
> **Note:** This guide assumes you can run Docker commands from a machine where > **Note:** This guide assumes you can run Docker commands from a machine where
> you are a member of the `docker` group, or have root privileges. Otherwise, you may > you are a member of the `docker` group or have root privileges. Otherwise, you
> need to add `sudo` to the example commands below. > may need to add `sudo` to the example commands below.
Docker will start the process of pulling the image from the Hub. Once it has completed, the Jenkins image should be visible in the output of a [`docker images`](https://docs.docker.com/reference/commandline/images) command, which lists your available images: Docker will start the process of pulling the image from the Hub. Once it has completed, the Jenkins image should be visible in the output of a [`docker images`](https://docs.docker.com/reference/commandline/images) command, which lists your available images:
$ docker images $ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
jenkins latest 1a7cc22b0ee9 6 days ago 662 MB jenkins latest 1a7cc22b0ee9 2 weeks ago 888 MB
> **Note:** Because the `pull` command did not specify any tags, it will pull > **Note:** Because the `pull` command did not specify any tags, it will pull
> the latest version of the public Jenkins image. If your enterprise environment > the latest version of the public Jenkins image. If your enterprise environment
> requires you to use a specific version, add the tag for the version you need > requires you to use a specific version, add the tag for the version you need
> (e.g., `jenkins:1.565`). > (e.g., `jenkins:1.609.2`).
## Customizing the Jenkins image ## Customizing the Jenkins image
@ -96,7 +96,7 @@ You'll do this by using a `Dockerfile` and the `docker build` command.
In order to add the new plugin and configure HTTPS access to the custom Jenkins In order to add the new plugin and configure HTTPS access to the custom Jenkins
image, you need to: image, you need to:
1. Create text file that defines the new plugin 1. Create a text file that defines the new plugin
2. Create copies of the private key and certificate 2. Create copies of the private key and certificate
All of the above files need to be in the same directory as the Dockerfile you All of the above files need to be in the same directory as the Dockerfile you
@ -143,7 +143,7 @@ following contents:
#Configure HTTP off and HTTPS on, using port 1973 #Configure HTTP off and HTTPS on, using port 1973
ENV JENKINS_OPTS --httpPort=-1 --httpsPort=1973 --httpsCertificate=/var/lib/jenkins/cert --httpsPrivateKey=/var/lib/jenkins/pk ENV JENKINS_OPTS --httpPort=-1 --httpsPort=1973 --httpsCertificate=/var/lib/jenkins/cert --httpsPrivateKey=/var/lib/jenkins/pk
The first `COPY` instruction in the above will copy the `plugin` file created The first `COPY` instruction in the above will copy the `plugins` file created
earlier into the `/usr/share/jenkins` directory within the custom image you are earlier into the `/usr/share/jenkins` directory within the custom image you are
defining with the `Dockerfile`. defining with the `Dockerfile`.
@ -188,17 +188,17 @@ customization.
Please note the use of the `-t` flag in the `docker build` command above. The Please note the use of the `-t` flag in the `docker build` command above. The
`-t` flag lets you tag an image so it can be pushed to a custom repository. In `-t` flag lets you tag an image so it can be pushed to a custom repository. In
the example above, the new image is tagged so it can be pushed to the the example above, the new image is tagged so it can be pushed to the
`ci-infrastructure` Repository within the `dtr.yourdomain.com` registry (your `ci-infrastructure` repository within the `dtr.yourdomain.com` registry (your
local DTR instance). This will be important when you need to `push` the local DTR instance). This will be important when you need to `push` the
customized image to DTR later. customized image to DTR later.
A `docker images` command will now show the custom image alongside the Jenkins A `docker images` command will now show the custom image alongside the Jenkins
image pulled earlier: image pulled earlier:
$ sudo docker images $ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
dtr.yourdomain.com/ci-infrastructure/jnkns-img latest fc0ab3008d40 2 minutes ago 674.5 MB dtr.yourdomain.com/ci-infrastructure/jnkns-img latest fc0ab3008d40 2 minutes ago 888.1 MB
jenkins latest 1a7cc22b0ee9 6 days ago 662 MB jenkins latest 1a7cc22b0ee9 2 weeks ago 888 MB
## Pushing to Docker Trusted Registry ## Pushing to Docker Trusted Registry
@ -233,7 +233,8 @@ Now that you’ve created the custom image, it can be pushed to DTR using the
492ed3875e3e: Image successfully pushed 492ed3875e3e: Image successfully pushed
fc0ab3008d40: Image successfully pushed fc0ab3008d40: Image successfully pushed
You can view the traffic throughput from the custom image being pushed on the DTR Dashboard: You can view the traffic throughput from the custom image being pushed, by selecting `Network` from the `Load Balancer` tile on the DTR Dashboard:
![](http://i.imgur.com/8KlHj9u.png)
![DTR console push throughput](../assets/console-push.png) ![DTR console push throughput](../assets/console-push.png)
@ -256,16 +257,14 @@ command from any Docker Host that has access to your DTR instance:
dtr.yourdomain.com/ci-infrastructure/jnkns-img: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. dtr.yourdomain.com/ci-infrastructure/jnkns-img: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.
Status: Downloaded newer image for dtr.yourdomain.com/ci-infrastructure/jnkns-img:latest Status: Downloaded newer image for dtr.yourdomain.com/ci-infrastructure/jnkns-img:latest
You can view the traffic throughput from the custom image being pulled on the DTR Dashboard: You can view the traffic throughput from the custom image being pulled on the DTR Dashboard.
![DTR console pull throughput](../assets/console-pull.png)
Now that the `jnkns-img` image has been pulled locally from DTR, you can view it Now that the `jnkns-img` image has been pulled locally from DTR, you can view it
in the output of the `docker images` command: in the output of the `docker images` command:
$ docker images $ docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
dtr.yourdomain.com/ci-infrastructure/jnkns-img latest fc0ab3008d40 8 minutes ago 674.5 MB dtr.yourdomain.com/ci-infrastructure/jnkns-img latest fc0ab3008d40 2 minutes ago 888.1 MB
## Launching a custom Jenkins container ## Launching a custom Jenkins container