9c0d25f349
The approach of having the proxy serve the local data as well as the remote wasn't working -- it seems that the proxy would always check upstream and prefer that data even if it had been pushed locally. To correct this, separate the data stores of the two registries, and add both of them to the registry_mirror setting for the docker daemon. Now we will pull from our buildset registry first, and fall back on the proxy to talk to upstream if an image is not found locally. The proxy is still required in order to mask out the username and password which dockerd will otherwise use when talking to upstream. Change-Id: Iab11954a4b5431d3b1a4d4753f519b6b71f64094
1.0 KiB
1.0 KiB
Adds a buildset registry to the docker configuration.
Use this role on any host which should use the buildset registry.
Role Variables
Information about the registry, as returned by :zuul
run-buildset-registry.The host (IP address) of the registry.
The port on which the registry is listening.
The port on which the registry proxy is listening.
The username used to access the registry via HTTP basic auth.
The password used to access the registry via HTTP basic auth.
The (self-signed) certificate used by the registry.