Skip to content

container/image

Image to run for a container created by the generic containerStart action.

The OCI image containerStart runs, e.g. my-runner:latest.

The image is resolved the same way the machine-bound runner path resolves a context image: it is loaded through the plugin's image handling and, when needed, pulled or tagged using container/registry (or the plugin's configured default registry when that is left empty) before the container is created.

Image resolution -- and any upload it requires -- happens on every containerStart call, whether or not an existing container named container/name ends up being reused rather than created. A caller re-attaching to a container it started earlier must still pass an image value that resolves successfully, even though the resolved image is not used to create anything in that case.

Never set this on the global profile. Action parameters aggregate from the global profile the same way plugin Config parameters do, so a container/image set there is silently supplied to every containerStart call that does not pass one explicitly -- creating a container from an image the caller never chose. Always pass this per call. The plugin logs the container/name and container/image it resolved at Info level so this is at least diagnosable if it happens.

Objects that Reference container/image

Not used in current content packs

Objects used by container/image

Not used in current content packs