From 9baf07a10466db47c4872030d3e9a883ba95f3d7 Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Wed, 22 Mar 2023 09:34:54 +1100 Subject: [PATCH] container role docs : clarify requirements 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 --- roles/build-container-image/common.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/roles/build-container-image/common.rst b/roles/build-container-image/common.rst index 6e304a553..f3dcf6377 100644 --- a/roles/build-container-image/common.rst +++ b/roles/build-container-image/common.rst @@ -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**