Mention "docker login" in push/pull documentation

It was suggested to me that documentation for "docker pull" and "docker
push" should reference "docker login", to make clearer how to specify
credentials for a push or pull operation. Add a note to the manual pages
and reference documentation explaining how registry credentials are
managed.

Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>
This commit is contained in:
Aaron Lehmann 2016-03-28 17:10:11 -07:00 committed by Tibor Vass
parent 85f983178b
commit 5161f2dc15
4 changed files with 8 additions and 0 deletions

View File

@ -165,6 +165,8 @@ listening on port 5000 (`myregistry.local:5000`):
$ docker pull myregistry.local:5000/testing/test-image $ docker pull myregistry.local:5000/testing/test-image
``` ```
Registry credentials are managed by [docker login](login.md).
Docker uses the `https://` protocol to communicate with a registry, unless the Docker uses the `https://` protocol to communicate with a registry, unless the
registry is allowed to be accessed over an insecure connection. Refer to the registry is allowed to be accessed over an insecure connection. Refer to the
[insecure registries](daemon.md#insecure-registries) section for more information. [insecure registries](daemon.md#insecure-registries) section for more information.

View File

@ -22,3 +22,5 @@ registry or to a self-hosted one.
Killing the `docker push` process, for example by pressing `CTRL-c` while it is Killing the `docker push` process, for example by pressing `CTRL-c` while it is
running in a terminal, will terminate the push operation. running in a terminal, will terminate the push operation.
Registry credentials are managed by [docker login](login.md).

View File

@ -151,6 +151,8 @@ listening on port 5000 (`myregistry.local:5000`):
$ docker pull myregistry.local:5000/testing/test-image $ docker pull myregistry.local:5000/testing/test-image
Registry credentials are managed by **docker-login(1)**.
Docker uses the `https://` protocol to communicate with a registry, unless the Docker uses the `https://` protocol to communicate with a registry, unless the
registry is allowed to be accessed over an insecure connection. Refer to the registry is allowed to be accessed over an insecure connection. Refer to the
[insecure registries](https://docs.docker.com/engine/reference/commandline/daemon/#insecure-registries) [insecure registries](https://docs.docker.com/engine/reference/commandline/daemon/#insecure-registries)

View File

@ -44,6 +44,8 @@ Check that this worked by running:
You should see both `rhel-httpd` and `registry-host:5000/myadmin/rhel-httpd` You should see both `rhel-httpd` and `registry-host:5000/myadmin/rhel-httpd`
listed. listed.
Registry credentials are managed by **docker-login(1)**.
# HISTORY # HISTORY
April 2014, Originally compiled by William Henry (whenry at redhat dot com) April 2014, Originally compiled by William Henry (whenry at redhat dot com)
based on docker.com source material and internal work. based on docker.com source material and internal work.