[Pulp-dev] Naming/Tagging-Schema for container images

Dennis Kliban dkliban at redhat.com
Mon May 18 12:46:00 UTC 2020


Long term, I would like to stop publishing container images based on
Fedora. Images for production use should be built on top of CentOS 8
stream[0]. The name of the image repository should not contain the OS name.

Each 3.y release of pulpcore should live in its own repository called
pulp/pulp-3-y. The initial release should be tagged as both 'latest' and
'0'. Each time a compatible plugin is released, this image should be
updated and the tag should be incremented by 1. The project website should
contain a table that is automatically generated. The table should list what
versions of plugins are included in each of the tags.

What do others think?

[0] https://pulp.plan.io/issues/6676


On Thu, May 14, 2020 at 12:54 PM Matthias Dellweg <mdellweg at redhat.com>
wrote:

> We have recently started a new repository calles pulp-oci-images that
> should emit according to its name OCI compatible images with pulp
> installed.
> In the first go, this includes the single-container promoted though
> this blog post [0].
> Soon to be added is the base container image that shall speed up our CI
> [1].
> In the future, i envision a similar single-container solution based on
> centos instead of fedora,
> as well as ci base images based on centos having python3.6 installed.
> Does anyone think, we even need different ci-images for pulp release
> branches?
>
> The big question now is: How are we going to name and tag those images?
>
> The one from [0] is called "pulp/pulp-fedora31:latest".
> We could go with that and add names like:
> - "pulp/pulp-centos8:3.2"
>   installation of core version 3.2 with all compatible plugins on centos8
> - "pulp/pulp-ci-fedora32:latest"
> - "pulp/pulp-ci-centos8:latest"
>
> BTW, the ci-base images can be built by using the same Conteinerfile
> interrupted early.
> (with --target in a multistage build)
>
> What do you think?
>
> [0] https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
> [1]
> https://github.com/pulp/pulpcore/blob/master/.travis/Containerfile.ci_base
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20200518/3e3de9d9/attachment.htm>


More information about the Pulp-dev mailing list