UBI/RHEL 9 based solvers

[fridex]

Is your feature request related to a problem? Please describe.

Let's monitor release cycle of UBI/RHEL 9 and provide relevant solvers to the deployment once they are available and ready to be used.

[fridex]

/sig stack-guidance /priority important-soon

[codificat]

Related: https://github.com/thoth-station/core/issues/342

[fridex]

@Gregory-Pereira worked on a similar item in https://github.com/thoth-station/s2i-thoth/issues/231, related docs:

• https://github.com/thoth-station/s2i-thoth#updating-and-releasing-new-container-images
• https://github.com/thoth-station/thoth-application/blob/master/docs/thoth_s2i_procedure.md

The procedure is very similar, we need to wait for a stable UBI/RHEL 9 Python s2i.

[Gregory-Pereira]

I will go ahead and take a look at this as well. /assign

[fridex]

I will go ahead and take a look at this as well.

Thanks 💯 Worth checking the current state of UBI/RHEL 9 Python s2i. If they are considered stable, we should wait.

[Gregory-Pereira]

So it looks like there is some Red Hat documentation saying that it exists, yet when I try to pull the ubi9 image like the ubi8 one it can't find it.

$ podman pull registry.access.redhat.com/ubi8/ubi
Trying to pull registry.access.redhat.com/ubi8/ubi:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob de9bc33d7337 skipped: already exists  
Copying blob effc4ea612c8 skipped: already exists  
Copying config b1b0a30a72 done  
Writing manifest to image destination
Storing signatures
b1b0a30a7282d9c9387499c2ef7992bd19958e7bb533904c1a316991b4739424
$ podman pull registry.access.redhat.com/ubi9/ubi
Trying to pull registry.access.redhat.com/ubi9/ubi:latest...
WARN[0000] failed, retrying in 1s ... (1/3). Error: initializing source docker://registry.access.redhat.com/ubi9/ubi:latest: reading manifest latest in registry.access.redhat.com/ubi9/ubi: unknown: Not Found 
WARN[0001] failed, retrying in 1s ... (2/3). Error: initializing source docker://registry.access.redhat.com/ubi9/ubi:latest: reading manifest latest in registry.access.redhat.com/ubi9/ubi: unknown: Not Found 

This either means 1, it doesn't exist yet, or 2, the repo configuration for the ubi9 image is different from that of ubi8. I have tried a variation for rhel9 as well, and still no luck.

It appears to be in Beta right now: Red Hat provides Red Hat Enterprise Linux Beta access to all subscribed Red Hat accounts.

[fridex]

@frenzymadness, could you please let us know the current state for UBI 9 Python s2i? What is its state and when it could become stable? Thanks in advance.

[frenzymadness]

Hi. UBI9 is still beta and we haven't started building our Python container image on top of that yet. We are currently working on Centos stream 9: https://github.com/sclorg/s2i-python-container/pull/501 But there are some blockers.

I see the image in the catalog: https://catalog.redhat.com/software/containers/ubi9-beta/ubi/60a6ea70f13ea7781b9fd615?container-tabs=gti

But I also cannot pull it:

Trying to pull registry.access.redhat.com/ubi9-beta/ubi:9.0.0beta-892...
Error: Source image rejected: None of the signatures were accepted, reasons: Invalid GPG signature: gpgme.Signature{Summary:128, Fingerprint:"938A80CAF21541EB",…

[fridex]

Thanks, @frenzymadness. We will wait for the stable release then. Thanks again 👍🏻

/lifecycle frozen

[goern]

@codificat could you work with @Gregory-Pereira on this? thx!

[harshad16]

A new image is available now: https://catalog.redhat.com/software/containers/ubi9/python-39/61a61032bfd4a5234d59629e?tag=1-59&push_date=1656417750000 probably time to re-visit this.

[frenzymadness]

We are working on Python container image based on UBI 9: https://github.com/sclorg/s2i-python-container/pull/528

My estimation is that it should be finished this week.