Re: [yocto-autobuilder-helper][PATCH 07/11] config.json: add 'containers-' build jobs

On Mon, May 11, 2026 at 1:52 AM Paul Barker <[email protected]> wrote:

> On Thu, 2026-05-07 at 18:25 -0700, [email protected] wrote:
> > From: Tim Orling <[email protected]>
> >
> > Add 'containers-' build jobs that build container images on top
> > of the vcontainer-tarball SDK:
> >
> >   * containers-meta-virt: the original app-container-* images that
> >     ship in meta-virtualization itself (e.g. app-container-curl).
> >   * containers-library: a layer for additional images modelled
> >     after docker.io/library/*, sourced from meta-yocto-containers-demo
>
> I think we should combine these into one build job.
>

For now, that is impractical unless we use a branch of meta-virt that I can
control (because the container recipes are in flux). Or I would have to
continue running builds with a custom yocto-autobuilder-helper and a custom
meta-virt branch which defeats the purpose of pushing the containers to the
official registry.yocto.io and quay.io/yocto.

Let me put it another way: the container recipes in meta-virt are a simpler
demonstration. The container recipes in meta-yocto-containers-demo are
heading towards being fully signed/attested and hardened. So to me it made
sense to keep the jobs separate.


>
> What's the plan for meta-yocto-containers-demo? Should we host that on
> git.yoctoproject.org, or will the contents eventually be merged into
> meta-virtualization?
>

I haven't discussed this with Bruce, but I think it makes sense to have the
official list in meta-virtualization, when they are ready. The other main
reason for the meta-yocto-container-demo layer is for things like the
slsa-provenance.bbclass before submitting that to oe-core.


> Best regards,
>
> --
> Paul Barker
>
>