The existing AlmaLinux bootc images are outdated and use insecure features of buildah/podman (which is why an older version must be used).
Based on my existing images for Rocky Linux, I’ve turned them into AlmaLinux ones.
You can find them here.
Note that the default branch is still r9 (Rocky Linux 9), so change the branch to a9 or a10s (AlmaLinux 9 & AlmaLinux Kitten 10 respectively).
The existing AlmaLinux bootc images are outdated and use insecure features of buildah/podman
Can you elaborate?
This was the RHSA if I recall correctly: https://access.redhat.com/errata/RHSA-2025:0923
Ever since, the builds would fail, because now FROM can’t access files created during the build process using mounts, from a multi-stage build.
A quick solution to this is to just use rpm-ostree directly when building, that avoids this.
Hm, thanks for clarifying!
It looks like CentOS Stream has changed the way to create an image, so maybe AlmaLinux should follow suit as well.
Yes, they did, presumably to accommodate that. But that relies on versions of packages not available in general availability versions of EL. EL 9.7 & EL 10.1 (might be 10.2, having trouble in my head) will have them for sure, EL 9.6 & 10.0 might, but the betas don’t seem to.
Which is why my project uses AlmaLinux Kitten for the base image, as those versions are available there.
The images have been discontinued. For the archived source code, check out GitHub - charles25565/almalinux-bootc-archive: AlmaLinux unofficial bootc images - Archive
(check this for an updated URL)
The images are back now.
I plan on no longer maintaining my Rocky ones as I currently have 4 different codebases of mostly duplicated code. Knocking it down to 2 would be great.
Do note the AlmaLinux 9 images are based on AlmaLinux 9.6, which is currently a beta.
Below is an explanation of the branch names.
| Branch | What it is |
| a9 | AlmaLinux 9 |
| a10s | AlmaLinux 10 Kitten (s is for Kitten) |