Repository navigation
feat(ubi): Add and use UBI10 base image #1349
Description
Activity
I'm happy to work on this after I've completed the work for stackabletech/stackablectl#220.
@lfrancke do we need to keep the UBI9 image around (I recall needing to keep the UBI8 image maintained for some time before we dropped it)?
Help me with that question: I personally don't need it. But should we need to release a patch for e.g. 25.11 would we need the old base image around?
And if so: We don't want to ship an image based on a UBI9 that hasn't been updated for a year.That was my only "fear" here. If that is irrational or I'm missing something then it can go. That is the only thing I want to make sure of: Being able to easily release patches for our supported SDP versions if needed.
But should we need to release a patch for e.g. 25.11 would we need the old base image around?
I think we have enough safe-guards should that happen:
- We have the release images in Harbor
- Edit: We have nightly images, but not a tagged image for the ubi9-rust-builder: https://oci.stackable.tech/harbor/projects/12/repositories/ubi9-rust-builder/artifacts-tab
- We have git and can revert the commit that removes it just to rebuild it if we need
- We could just use ubi10 (provided we don't run into any major issues building the nightly images).
So I'd be fine with dropping it when we can show that we can build images on ubi10. Also happy to just keep it around for a release if that eases concern.
- We have the release images in Harbor
I'm happy to defer that decision to you. That was my only concern.
- moved this from Ready for Development to Development: In Progress in Stackable Engineering
on Dec 1, 2025 - moved this from Selected for Development to In Progress in Stackable End-to-End Coordination
on Dec 3, 2025 Reverted the PR with #1364 and will reopen this issue (which is pending boost-devel being available in UBI10 or EPEL10).
Upstream issue that's blocking us: https://issues.redhat.com/browse/RHEL-136868
@lfrancke, I haven't seen any movement on the upstream issue. Do you want to ping them or is it still too early?
Using UBI 10 would help our supply chain security a lot, because it currently has no known vulnerabilities, compared to UBI 9 which currently has 80 vulnerabilities according to Trivy.
Reacted by Lukas Krug and Lars FranckeIn the version bump meeting today, we decided to wait until there is a response from RedHat (Lars has raised it in the partner portal too).
Reacted by Lars FranckeWe have decided to install boost libraries ourselves, as they will not be part of EPEL10.
We decided to skip this for 26.7 and will pick it up again for 26.11.
Reasons: a) We're close to the release and b) upstream work happening in Hadoop which we'd like to wait for- moved this from In Progress to In Refinement in Stackable End-to-End Coordination
on Aug 19, 2026
This issue tracks the addition and usage/replacement of the UBI10 base image. There are currently two options:
There already is a branch which includes a few basic changes to add and build the UBI10 image. This PoC worked and an image could be built, but the image was not tested to be used as the base of our operator container images.