| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Adding -e REGISTRY_PROXY_REMOTEURL=https://registry-1.docker.io to the
docker run command in the start-registry script configures the local
registry as a pull through cache. However, pushing of images to the
local registry fails.
Pushing to a registry configured as a pull-through cache is unsupported.
For more information, reference the proxy section in Docker
Documentation (https://docs.docker.com/registry/configuration/)
Corresponding change to the documentation has been made to the
multinode.rst file in the Kolla-ansible repository
https://review.openstack.org/#/c/426858/
Change-Id: I636912f9958490bf751bfa0f449998c61d273241
Closes-Bug: #1659738
|
|
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
|
|
* Remove duplicated info between the 'image-building' and 'multinode'
guides regarding deploying a local insecure registry.
* Add a helper script to easily start a local registry in a consistent
way.
* Remove warnings around bugs in older registries, 2.3+ is now the
default
* Remove references to running the local registry on port 4000, this
causes confusion as Docker expects port 5000 by default unless
specified, and registries are not required for all-in-one deployments
anyhow.
TrivialFix
Change-Id: I89f231df09102e3f1d5f21c8a8ca938ea60ae95b
|
