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
44 lines
1.1 KiB
ReStructuredText
44 lines
1.1 KiB
ReStructuredText
Runs a docker registry for the use of this buildset.
|
|
|
|
This may be used for a single job running on a single node, or it may
|
|
be used at the root of a job graph so that multiple jobs running for a
|
|
single change can share the registry. Two registry endpoints are
|
|
provided -- one is a local registry, the second is an upstream proxy.
|
|
|
|
**Role Variables**
|
|
|
|
.. zuul:rolevar:: buildset_registry_root
|
|
:default: {{ ansible_user_dir }}/buildset_registry
|
|
|
|
Path for the registry volumes.
|
|
|
|
**Return Values**
|
|
|
|
.. zuul:rolevar:: buildset_registry
|
|
|
|
Information about the registry.
|
|
|
|
.. zuul:rolevar:: host
|
|
|
|
The host (IP address) of the registry.
|
|
|
|
.. zuul:rolevar:: port
|
|
|
|
The port on which the registry is listening.
|
|
|
|
.. zuul:rolevar:: proxy_port
|
|
|
|
The port on which the proxy is listening.
|
|
|
|
.. zuul:rolevar:: username
|
|
|
|
The username used to access the registry via HTTP basic auth.
|
|
|
|
.. zuul:rolevar:: password
|
|
|
|
The password used to access the registry via HTTP basic auth.
|
|
|
|
.. zuul:rolevar:: cert
|
|
|
|
The (self-signed) certificate used by the registry.
|