Use UBI9 based Quarkus micro image

[michalvavrik]

I have Kuberentes application that is failing over:

2025-02-11T23:37:09.2099788Z 23:37:09,153 INFO  [pingpong] [pingpong-5c5f8c5dd6-dkvr5] ./application: /lib64/libc.so.6: version `GLIBC_2.33' not found (required by ./application)
2025-02-11T23:37:09.2101368Z 23:37:09,153 INFO  [pingpong] ./application: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by ./application)
2025-02-11T23:37:09.2102362Z 23:37:09,153 INFO  [pingpong] ./application: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by ./application)

I believe the reason for this is combination of default quay.io/quarkus/ubi9-quarkus-mandrel-builder-image:jdk-21 and ubi8 based quay.io/quarkus/quarkus-micro-image.

This commit f95cf8c changed description of the quarkus.jib.base-native-image to say quay.io/quarkus/ubi9-quarkus-micro-image:2.0 is default, but didn't change default.

https://github.com/quarkusio/quarkus/wiki/Migration-Guide-3.19#ubi-9 says that UBI9 based micro image is default, I believe this will solve my issues. I experienced many similar issues when I combined UBI9 and UBI8. Thanks.

P.S. I have also mentioned that ubi-quarkus-native-binary-s2i didn't change to ubi9-quarkus-native-binary-s2i, but the difference is that it is not in the migration guide or in the configuration property javadoc io.quarkus.container.image.openshift.deployment.ContainerImageOpenshiftConfig#baseNativeImage and I always override it didn't hit issues yet. I wonder - is it intentional and why?

[github-actions]

🙈 The PR is closed and the preview is expired.

[gsmet]

LGTM but let's wait for Clément's approval.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 5ac3a00.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[cescoffier]

Definitely an overlook from my side! Thanks!

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 5ac3a00.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.