Re: [yocto-patches] [yocto-autobuilder-helper][PATCH v2 08/10] scripts: add container registry push, auth, tagging, runtime selection

On Mon, 2026-06-01 at 16:18 -0700, Tim Orling via lists.yoctoproject.org wrote:
> From: Tim Orling <[email protected]>
> 
> Add the push-containers infrastructure that drives the
> post-build steps for the 'containers-library' job. After
> each build step the runtime container store is harvested
> and pushed to one or more registries with derived per-step
> tags.
> 
> * config.json: add CONTAINER_REGISTRIES, CONTAINER_AUTH_CONFIG,
>   CONTAINER_RUNTIME, CONTAINER_TAG_CMDS, CONTAINER_VERSION_RECIPE
>   and CONTAINER_IMAGE_MAP configuration knobs.
> * scripts/run-config: drive push-containers as a post-step
>   action. Tags are generated from recipe and distro metadata
>   (yocto- tag uses major.minor on snapshots and full PV on
>   releases) with CONTAINER_VERSION_RECIPE allowing a step to
>   source PV from a different recipe than the image itself.
> * Registry auth is staged via .../config.json or podman
>   .../auth.json using CONTAINER_AUTH_CONFIG, replacing an
>   interactive login that could hang. CONTAINER_RUNTIME picks
>   between vdkr (Docker-compatible) and vpdmn (Podman) runtimes.
> * Robustness: skip gracefully when no registries are configured,
>   fix the OCI directory path, handle memres already running,
>   and avoid hanging when memres has not yet come up.
> 
> AI-Generated: Claude Cowork Opus 4.7
> Signed-off-by: Tim Orling <[email protected]>
> ---
>  config.json        |   5 ++
>  scripts/run-config | 129 +++++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 134 insertions(+)

This is adding way too much code for a specific use case to run-config.
This needs to be in a separate script (in the same way docs builds or
other things are).

Cheers,

Richard