Re: [yocto-patches] [yocto-autobuilder-helper][PATCH v2 10/10] config.json: add 'containers-library' build job

On Tue, Jun 2, 2026 at 4:02 AM Paul Barker via lists.yoctoproject.org <paul=
[email protected]> wrote:

> On Mon, 2026-06-01 at 16:18 -0700, Tim Orling via lists.yoctoproject.org
> wrote:
> > From: Tim Orling <[email protected]>
> >
> > Add 'containers-library' build job that build container images on top
> > of the vcontainer-tarball SDK:
> >
> >   * original container images from the intial "container-cross-install"
> >     branch of  meta-virtualization
> >     - container-base
> >     - app-container-curl
> >   * additional images modelled after docker.io/library/*
> >     - app-container-python
> >     - app-container-mosquitto
> >     - app-container-valkey
> >     - app-container-nginx
> >   * Tag containers with versions based on the recipe to which they are
> >     mapped, e.g. python:3, python:3.14, python:3.14.5.
>
> These version tags may exist in docker library/hardened images, but are
> they actually appropriate for the images we create?
>

They are tagged with 'wrynose' and 'yocto-6.0' (and release builds would be
tagged with full 'yocto-6.0.n').

We need to think about container consumers, not just Yocto users. Container
consumers want to know
what version of the tool is in the container they are consuming, so we
should follow the same tagging
pattern. Tags are cheap (they are just an alias for the same hash).


>
> I would expect python:master, python:blacksail, etc tags which track our
> branches.
>
> Best regards,
>
> --
> Paul Barker
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#4112):
> https://lists.yoctoproject.org/g/yocto-patches/message/4112
> Mute This Topic: https://lists.yoctoproject.org/mt/119603250/924729
> Group Owner: [email protected]
> Unsubscribe:
> https://lists.yoctoproject.org/g/yocto-patches/leave/13169857/924729/1023951714/xyzzy
> [[email protected]]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
>