Right now, there are bootc images at https://quay.io/repository/centos-bootc/centos-bootc that come from https://gitlab.com/redhat/centos-stream/containers/bootc
On Mon, Nov 25, 2024 at 7:01 AM Troy Dawson tdawson@redhat.com wrote:
The CentOS Alternative Images SIG has recently been asked about making CentOS bootc images.[1]
Investigation is showing that we should be able to. But that leads to the next question. After we build them, where would they go?
(A) Initial thoughts are someplace in the CentOS SIG infrastructure. But there currently isn't anything setup for serving containers. It's also not the first place people would look.
I was thinking of having them on quay.io. But if we do publish our bootc/container images on quay.io, where?
(B) centos:<some-name> ? That would mean that the SIG's would have access to that account. I also don't know what we would have for <some-name>. We would have to have something different for each SIG.
(C) centos-sig:<some-name> ? The SIG's would still have to share authentication in some manner. I still don't know what to do for the names.
(D) centos-<sig-name>:<some-name> The SIG's would have their own authentication. The sig's would have control of their own naming convention. centos-altimages:stream10-bootc centos-altimages:stream10-bootc-kde centos-isa:stream9-bootc-baseline centos-isa:stream9-bootc-optimized There are some drawbacks for this. Someone would have to know the SIG name to find the image. Possibly other things.
I personally am leaning towards (D). But I could be persuaded towards the others. And it's possible I haven't even thought of the correct solution.
Ideas / thoughts / comments welcomed and wanted.
Troy
[1] - https://pagure.io/centos-sig-alt-images/sig/issue/10
devel mailing list -- devel@lists.centos.org To unsubscribe send an email to devel-leave@lists.centos.org