zuul-jobs/roles/run-buildset-registry
James E. Blair 8998838d7a run-buildset-container: fix username/password for proxy registry
This configuration is intended to mask the creds supplied by the
local docker configuration when the registry is used as a
pull-through proxy to upstream.  But we need to set the creds
to the empty string, rather than null, which ends up as the string
"None" in the docker config.

Change-Id: Ic36a5c764dec8df4fa460f6735ff5668a1dd3b50
2019-02-22 13:22:19 -08:00
..
defaults Add a role to run a buildset registry 2019-02-01 13:25:11 -08:00
tasks run-buildset-container: fix username/password for proxy registry 2019-02-22 13:22:19 -08:00
README.rst run-buildset-registry: run a dual registry 2019-02-21 13:49:49 -08:00

README.rst

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 read-only endpoint which acts as a pull-through proxy and serves upstream images as well as those which are pushed to the registry. The second is intended only for pushing images.

Role Variables

Return Values

Information about the registry.

The host (IP address) of the registry.

The port on which the registry is listening.

The host (IP address) to use when pushing images to the registry.

The port to use when pushing images to the registry.

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.