[Pulp-dev] Naming/Tagging-Schema for container images
mdellweg at redhat.com
Fri May 15 07:03:24 UTC 2020
Thank you for bringing this up.
With ci-base-image i mean images used (currently) in all travis pipelines,
including testing and releasing machinery. They are not meant for direct
The difference between this base image and the user-consumable
single-container image is however only a pip installation of pulp-packages
and copying of webserver config snippets.
So do you think, those molecule images should be included in the naming
convention? Or should we just try not to produce collisions?
On Thu, May 14, 2020 at 9:02 PM Mike DePaulo <mikedep333 at redhat.com> wrote:
> On Thu, May 14, 2020 at 12:54 PM Matthias Dellweg <mdellweg at redhat.com>
>> We have recently started a new repository calles pulp-oci-images that
>> should emit according to its name OCI compatible images with pulp
>> In the first go, this includes the single-container promoted though
>> this blog post .
>> Soon to be added is the base container image that shall speed up our CI
>> 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
> When you say "ci images", you mean images meant for user consumption? Or
> images only used in CI testing?
>> The big question now is: How are we going to name and tag those images?
>> The one from  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"
> Remember that our current images like "
> https://quay.io/repository/pulp/pulp-ci-f31" are only used for CI testing
> of upgrades. The description states:
> "Images of Pulp on Fedora 31, for CI testing of ansible-pulp performing
> In fact, they are built via ansible molecule.
>> 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?
>>  https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Mike DePaulo
> He / Him / His
> Service Reliability Engineer, Pulp
> Red Hat <https://www.redhat.com/>
> IM: mikedep333
> GPG: 51745404
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev