zuul/zuul-jobs
Code Issues Proposed changes

container role docs : clarify requirements

Browse Source 
skopeo is used from the executor in the promote process, but isn't
required to be installed on nodes with ensure-skopeo.  Clarify this
and the runtime requirements.

Change-Id: Ifaf4b788117986037b124972441b1884744374e5
This commit is contained in:
Ian Wienand 2023-03-22 09:34:54 +11:00
parent 75c0f2ebaa
commit 9baf07a104
No known key found for this signature in database
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
roles/build-container-image/common.rst
View File

@ -34,9 +34,10 @@ They all accept the same input data, principally a list of
dictionaries representing the images to build. YAML anchors_ can be
used to supply the same data to all three jobs.
Use the :zuul:role:`ensure-skopeo` role as well as the
:zuul:role:`ensure-docker`, or :zuul:role:`ensure-podman` roles before
using the roles described here.
The build and upload roles require a container runtime that should be
installed before use; for example by using either the
:zuul:role:`ensure-docker` or :zuul:role:`ensure-podman` roles. The
promote job assumes `skopeo` is available on the executor.
**Role Variables**