zuul-jobs/roles/run-buildset-registry
Monty Taylor 63bd307e63 Support multi-arch image builds with docker buildx
Docker has experimental support for building multi-arch
container images with a buildx command. Currently it only
supports pushing to a registry after running and the images
don't end up in the local docker images list. To work around
that, push to the buildset registry then pull back. This
is the inverse of the normal case where we build, then
retag, then push. The end result should be the same.

Change-Id: I6a4c4f9e262add909d2d5c2efa33ec69b9d9364a
2020-05-04 14:02:13 -05:00
..
defaults use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00
tasks Support multi-arch image builds with docker buildx 2020-05-04 14:02:13 -05:00
templates Test buildset registry with k8s and docker 2019-10-28 15:45:39 -07:00
README.rst use-buildset-registry: Add podman support 2019-12-05 11:44:15 -08:00

Runs a container 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.

Role Variables

Return Values

Information about the registry.

The host (IP address) of the registry.

The port on which the registry 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.