publish fedora-based container on registry.fedoraproject.org about s2i-perl-container HOT 5 CLOSED

I have no idea how images for Fedora are built and published. But what prevented perl images from building in the past was that Fedora did not contain the needed Modularity modules and Perl versions. Now Fedora ≥ 34 contains all the necessary stuff. But I worry that the underlying Fedora images (s2i-base etc.) are require an older Fedora (e.g. 33).

from s2i-perl-container.

Yeah, one issue is that s2i-core and s2i-base are not yet built for f34, but that can now be done after having F33 branched.

For the perl image if the underlying modules are available now we would first need to add a new version (3.22) in this repository that contains the Fedora-based Dockerfile built on top of f34/s2i-base.
After that the sources need to be synced downstream to the Fedora's dist-git. This can be done manually, or with cwt (cwt --do-image perl git pullupstream), but cwt will be missing the configs for f34.
The build and publishing of the resulting image is done similarly to how rpms are done.

We will get to all of it eventually, but if you would like to help with any of the steps I would be glad to review any PRs you might prepare. :)

from s2i-perl-container.

This can be close. perl-5.32 is published here https://quay.io/repository/fedora/perl-532

from s2i-perl-container.

The rest containers like perl-5.34 will be published there as well. Like https://quay.io/repository/fedora/perl-534

from s2i-perl-container.

@phracek What about perl-5.30? We have it in repository, but not in quay.io. Same perl-5.26.

from s2i-perl-container.