aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMatt McEuen <mm9745@att.com>2016-12-21 17:18:07 -0600
committerMatt McEuen <mm9745@att.com>2017-01-06 19:48:58 +0000
commit19b0defb9220ff55e16f857dd6741b7e16a44bc7 (patch)
treec412236d1f8c75123c9029b2d150cfba942dec50
parentfaea5b91141406c82bd2e029da9aeeb9afa8a200 (diff)
downloadkolla-19b0defb9220ff55e16f857dd6741b7e16a44bc7.tar.gz
kolla-19b0defb9220ff55e16f857dd6741b7e16a44bc7.zip
Configure local registries to proxy docker hub
Added the REGISTRY_PROXY_REMOTEURL parameter to the registry creation script, so that the registry will mirror images from Docker Hub (while still being able to host custom-built images). Updated the Multinode guide to reflect this. Change-Id: Ib789241fd2947b06fb0dc5732a0bf28431e1403d Closes-Bug: #1647436
-rw-r--r--doc/multinode.rst4
-rwxr-xr-xtools/start-registry1
2 files changed, 5 insertions, 0 deletions
diff --git a/doc/multinode.rst b/doc/multinode.rst
index 24938edaf..b88a248ff 100644
--- a/doc/multinode.rst
+++ b/doc/multinode.rst
@@ -35,6 +35,10 @@ Configure Docker on all nodes
.. note:: As the subtitle for this section implies, these steps should be
applied to all nodes, not just the deployment node.
+The ``start-registry`` script configures a docker registry that proxies Kolla
+images from Docker Hub, and can also be used with custom built images (see
+:doc:`image-building`).
+
After starting the registry, it is necessary to instruct Docker that it will
be communicating with an insecure registry. To enable insecure registry
communication on CentOS, modify the ``/etc/sysconfig/docker`` file to contain
diff --git a/tools/start-registry b/tools/start-registry
index 7c29e13a1..cb9715149 100755
--- a/tools/start-registry
+++ b/tools/start-registry
@@ -5,4 +5,5 @@ docker run -d \
--restart=always \
-p 5000:5000 \
-v registry:/var/lib/registry \
+ -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io \
registry:2