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>
| ... | ... |
@@ -165,6 +165,8 @@ listening on port 5000 (`myregistry.local:5000`): |
| 165 | 165 |
$ docker pull myregistry.local:5000/testing/test-image |
| 166 | 166 |
``` |
| 167 | 167 |
|
| 168 |
+Registry credentials are managed by [docker login](login.md). |
|
| 169 |
+ |
|
| 168 | 170 |
Docker uses the `https://` protocol to communicate with a registry, unless the |
| 169 | 171 |
registry is allowed to be accessed over an insecure connection. Refer to the |
| 170 | 172 |
[insecure registries](daemon.md#insecure-registries) section for more information. |
| ... | ... |
@@ -151,6 +151,8 @@ listening on port 5000 (`myregistry.local:5000`): |
| 151 | 151 |
|
| 152 | 152 |
$ docker pull myregistry.local:5000/testing/test-image |
| 153 | 153 |
|
| 154 |
+Registry credentials are managed by **docker-login(1)**. |
|
| 155 |
+ |
|
| 154 | 156 |
Docker uses the `https://` protocol to communicate with a registry, unless the |
| 155 | 157 |
registry is allowed to be accessed over an insecure connection. Refer to the |
| 156 | 158 |
[insecure registries](https://docs.docker.com/engine/reference/commandline/daemon/#insecure-registries) |
| ... | ... |
@@ -44,6 +44,8 @@ Check that this worked by running: |
| 44 | 44 |
You should see both `rhel-httpd` and `registry-host:5000/myadmin/rhel-httpd` |
| 45 | 45 |
listed. |
| 46 | 46 |
|
| 47 |
+Registry credentials are managed by **docker-login(1)**. |
|
| 48 |
+ |
|
| 47 | 49 |
# HISTORY |
| 48 | 50 |
April 2014, Originally compiled by William Henry (whenry at redhat dot com) |
| 49 | 51 |
based on docker.com source material and internal work. |