AlmaLinux, CentOS Stream, Oracle Linux and Rocky Linux
Alma, CentOS, Oracle, Rocky for users
Four files, 23 systems of the Red Hat compatible family: AlmaLinux and Rocky Linux 8 to 10, CentOS Stream 9 and 10, Oracle Linux 7 to 10, on x86_64 and aarch64 (Oracle 7 on x86_64 only); CentOS and Oracle 7 to 9 boot with BIOS on x86_64, the 8s on aarch64 with Fedora's EDK2, and each guest has a user named after its group.
On the map: systems
▶ Watch this deck — 7 scenes, ~5 min
Worth seeing first
- The support matrix — where these four sit among the other families
01 Four distributions, one family
The groups almalinux, centos, oracle and rocky hold 23 systems, named GROUP-cloud-RELEASE.ARCH, such as rocky-cloud-9.x86_64.
If you ship software for Red Hat Enterprise Linux, you probably test on a rebuild of it, since RHEL itself needs a subscription. image-garden has four of the family: AlmaLinux, CentOS Stream, Oracle Linux and Rocky Linux. Each is a group of its own, so the names work like ubuntu-cloud-24.04.x86_64, with the group first: rocky-cloud-9.x86_64, or oracle-cloud-7.x86_64. That's twenty-three systems, releases 7 to 10, on x86_64 and 64-bit Arm. This deck covers where each image comes from, which releases run where, how they boot, what the first boot gives you, and what's worth knowing before you test.
Details and sources
Details
- Four files, four groups:
Group=almalinux(almalinux.ini:4-6),Group=centos(centos.ini:4-6),Group=oracle(oracle.ini:4-6) andGroup=rocky(rocky.ini:4-6), allVariant=cloud. - 23 sections: AlmaLinux 6, CentOS 4, Oracle 7, Rocky 6. The example
[rocky-cloud-9.x86_64]is rocky.ini:22-27;[oracle-cloud-7.x86_64]is oracle.ini:10-15. - The README lists them as AlmaLinux, CentOS ("usually CentOS Stream"), Oracle Linux and Rocky Linux (README.md:610-681).
- That RHEL itself needs a subscription, and that these four rebuild or track it, is Red Hat's and the distributions' own description (derived, not in the source). image-garden's CI calls them "Enterprise Linux: RHEL and its rebuilds and derivatives" (.gitlab-ci.yml:819).
Read more
02 Four sources, three ways to check
AlmaLinux, CentOS and Rocky use latest images checked against a CHECKSUM list or a per-image .SHA256SUM file. Oracle's fixed builds have their SHA-256 hash written into image-garden itself.
Each distribution publishes its images its own way. AlmaLinux, CentOS and Rocky offer a file name with latest in it, always the newest build of a release, and image-garden uses those, keeping the build it fetched first until you clear the cache. Their checksums come from a list: one CHECKSUM file per directory for AlmaLinux and Rocky, a small file per image for CentOS. Oracle's images are fixed builds, such as update 9 of Oracle Linux 7, and Oracle lists their checksums on a web page, not in a file make can fetch. So image-garden carries the hash itself, right beside the URL.
Details and sources
Details
- AlmaLinux:
https://repo.almalinux.org/almalinux/R/cloud/ARCH/images/AlmaLinux-R-GenericCloud-latest.ARCH.qcow2, checked againsthttps://raw.repo.almalinux.org/almalinux/R/cloud/ARCH/images/CHECKSUM(almalinux.ini:8-48). - CentOS Stream:
https://cloud.centos.org/centos/R-stream/ARCH/images/CentOS-Stream-GenericCloud-R-latest.ARCH.qcow2, checked against the same URL plus.SHA256SUM(centos.ini:8-34). - Rocky Linux:
https://dl.rockylinux.org/pub/rocky/R/images/ARCH/Rocky-R-GenericCloud-Base.latest.ARCH.qcow2, checked againstCHECKSUMin the same directory (rocky.ini:8-48). - Oracle Linux: fixed template builds under
https://yum.oracle.com/templates/OracleLinux/OLR/uN/ARCH/, such asOL7U9_x86_64-kvm-b257.qcow2, each with a literalSHA256SUM=; the file's comment points at Oracle's templates page (oracle.ini:8-57). The hashes were added by hand (NEWS:510). SHA256SUMS=becomesdownload-with-sha256sums,SHA256SUM=becomesdownload-with-sha256sumwith the hash on the command line (rulegen.py:62-71, rulegen.py:496-517). The list is fetched once and kept asFILE.sha256sumsbeside the image; an image already in the cache that matches it is not fetched again (image-garden:460-559).- The
.urlrule depends only on the makefiles, and the cachedlatestfile keeps its name, so a newer build is fetched only after the cached file is removed, for example byimage-garden make distclean(rulegen.py:520-524, derived from the rules). - Formats seen on 21 November 2026: AlmaLinux's
CHECKSUMhasHASH NAMElines, Rocky's and CentOS's filesSHA256 (NAME) = HASHlines; the helper reads both (image-garden:75-92). That Oracle lists checksums only on its web page is derived from the INI comment and the hand-copied hashes.
03 Which releases run where
AlmaLinux and Rocky: 8, 9, 10. CentOS Stream: 9, 10. Oracle: 7 to 10, with 7 on x86_64 only. All on x86_64 and aarch64, nothing else.
Line the four up and the gaps show. AlmaLinux and Rocky Linux carry 8, 9 and 10. CentOS Stream starts at 9, since Stream 8 has ended. Oracle Linux reaches furthest back, to 7, but only on x86_64; its 8, 9 and 10 run on both architectures. Everything else is on x86_64 and 64-bit Arm, and nothing in this family goes further: no RISC-V, no s390x, no POWER. So on an x86 laptop, the aarch64 systems are emulated and slow, and on an Arm machine, it's the x86 ones. If you only need one of each release, AlmaLinux or Rocky covers 8 to 10 on both.
Details and sources
Details
- AlmaLinux 8, 9, 10 and Rocky Linux 8, 9, 10 on x86_64 and aarch64 (almalinux.ini:8-48, rocky.ini:8-48).
- CentOS Stream 9 and 10 on both (centos.ini:8-34).
- Oracle Linux 7 on x86_64 only; 8, 9 and 10 on both (oracle.ini:10-57; README.md:669-675).
- No section of the four files names riscv64, s390x, ppc64 or loongarch64 (the support matrix).
- That CentOS Stream 8 has reached its end, and that a foreign architecture is emulated with TCG, are derived; see six architectures for the machines and the slower emulated case.
Read more
04 Which firmware starts them
BIOS boot on x86_64 for centos-cloud-9, centos-cloud-10 and oracle-cloud-7 to 9: no firmware files. On aarch64, almalinux-cloud-8, oracle-cloud-8 and rocky-cloud-8 use Fedora's EDK2.
Most of this family boots with UEFI, but not all of it. On x86_64, CentOS Stream 9 and 10 and Oracle Linux 7, 8 and 9 boot with a BIOS: the CentOS images have no EFI system partition to start from. For you, that means a .run script with no firmware files next to it, and QEMU's own BIOS doing the starting. On 64-bit Arm, the 8s are the odd ones out. AlmaLinux 8, Oracle Linux 8 and Rocky Linux 8 ship a shim or grub older than what newer EDK2 enforces, so they boot with Fedora's build of EDK2 instead. The snap carries it; other installs download it by checksum.
Details and sources
Details
Boot=bioson x86_64:centos-cloud-9andcentos-cloud-10(centos.ini:8-27),oracle-cloud-7,-8and-9(oracle.ini:10-36). Every other x86_64 section of the four files, and every aarch64 one, saysBoot=efi.- The commit that moved CentOS to BIOS, 1583906, says: "The images do not have an ESP and cannot be used with EFI at present." No reason is recorded for Oracle.
- For
Boot=bios, rulegen.py writes the BIOS rules: the.runscript needs only the.qcow2, and the command line has no-drive if=pflash(rulegen.py:612-631, rulegen.py:803-808, mk/010-qemu-x86_64.mk:27-39). QEMU then uses its default BIOS, SeaBIOS (derived). almalinux-cloud-8,oracle-cloud-8androcky-cloud-8are inGARDEN_AARCH64_FEDORA_EDK2_SYSTEMS, with Fedora's EDK2 from the snap'sqemu-aarch64component or downloaded by checksum from image-garden's package registry (mk/010-qemu-aarch64.mk:114-167).
Read more
05 A user named after the group
Users root/root and GROUP/GROUP with passwordless sudo: almalinux, centos, oracle or rocky. Host name GROUP-RELEASE. No dnf or yum cache.
These cloud images come with a default user of their own, but image-garden's user-data lists its own users instead. Every system gets root, with password root, and a second user named after its group, with that same word as password and sudo without one. So on rocky-cloud-9 you log in as rocky, on oracle-cloud-7 as oracle, on centos-cloud-10 as centos. The .run script's --query prints both. The host name follows the group too: rocky-9. And as on Fedora, pkgproxy doesn't cache dnf or yum here: only snapd, if you install it, and Go modules go through it.
Details and sources
Details
- rulegen.py passes the group as the second user's name (rulegen.py:467); the common template makes
root/rootandGROUP/GROUPwithsudo: ["ALL=(ALL) NOPASSWD:ALL"](mk/010-qemu.mk:200-211). None of the four groups has a quirk template. --queryprintsvm.memory_mband the two users,rootand the group (mk/010-qemu.mk:57-90, rulegen.py:596).- The host name is
GROUP-RELEASE, asrocky-9(mk/010-qemu.mk:94-97). - With a pkgproxy, these groups get the
snapsetup script andGOPROXY, not the apt script, and there is no script for dnf or yum (mk/010-qemu.mk:127-180). - The images' own default users (such as
cloud-user,rockyoralmalinux) come from their cloud-init configuration; ausers:list withoutdefaultreplaces that user (derived, cloud-init behaviour).
06 Worth knowing before you test
EL 10 needs x86-64-v3: the default -cpu max passes the host's through, or set QEMU_CPU_X86_64=Haswell. SELinux enforcing; CentOS Stream runs ahead of RHEL; Oracle 7 is old.
Four things are worth knowing here. Release 10 of all four needs an x86-64-v3 processor, Haswell or newer. The default CPU model, max, hands the guest your host's CPU, so any recent machine is fine; on older hardware the README suggests setting QEMU_CPU_X86_64 to Haswell. SELinux is enforcing, as these distributions ship it. CentOS Stream isn't a rebuild of a RHEL release: it's where the next minor release of RHEL is made, so it can be ahead of what your users run. And Oracle Linux 7 is old; treat it as a long-tail check, not a modern baseline.
Details and sources
Details
- The README: "Rocky 10 (and other RHEL 10 derivatives) require at least Haswell CPU (x86_64-v3). Set
QEMU_CPU_X86_64=Haswellor newer if needed." (README.md:681);QEMU_CPU_X86_64defaults tomax(mk/010-qemu-x86_64.mk:6, README.md:896). It is a make variable, passed on the command line or set in.image-garden.mk(README.md:883-886); it is baked into the.runscript and the provisioning boot when they are made. - image-garden's CI: "EL 10 needs x86-64-v3, which every x86_64 KVM runner has … with QEMU's default -cpu max" (.gitlab-ci.yml:819-823).
- SELinux enforcing in these images; CentOS Stream as the development branch of the next RHEL minor release; Oracle Linux 7's age (its image is update 9 of release 7, oracle.ini:10-15): the distributions' own descriptions (derived, not in the source). Nothing in image-garden changes SELinux.
Read more
07 Where to go from here
Next: Fedora, Amazon Linux, boot types, UEFI firmware, the users, downloads and the support matrix.
So this family is four files, twenty-three systems, two ways to boot on x86, and a user named after each group. From here, the Fedora deck shows where the family's packages start out, and the Amazon Linux deck covers Amazon's own distribution. The boot types deck explains what bios changes, and the firmware deck where Fedora's EDK2 comes from. The users deck has the details of root and the group user, and the download deck how checksum lists and literal hashes are checked. The support matrix sets all four beside every other family.
Details and sources
Read more
Basis of the statements on this page
The tables are generated from data/almalinux.ini, data/centos.ini, data/oracle.ini and data/rocky.ini of image-garden at the commit in garden.commit ("code"). Users, host names, pkgproxy coverage and firmware are read in rulegen.py, mk/010-qemu.mk and mk/010-qemu-aarch64.mk ("code"). The checksum file formats were seen by fetching one of each on 21 November 2026 ("run"). What each distribution is, its default user and SELinux mode are the distributions' own descriptions ("derived").
Every system
Names are GROUP-cloud-RELEASE.ARCH. The checksum column names the checksum file, or the start of the hash image-garden carries itself.
| System | Arch | Boot | Image file | Checksum source | Section |
|---|---|---|---|---|---|
almalinux-cloud-8.x86_64 | x86_64 | efi | AlmaLinux-8-GenericCloud-latest.x86_64.qcow2 | CHECKSUM | almalinux.ini:8-13 |
almalinux-cloud-8.aarch64 | aarch64 | efi | AlmaLinux-8-GenericCloud-latest.aarch64.qcow2 | CHECKSUM | almalinux.ini:15-20 |
almalinux-cloud-9.x86_64 | x86_64 | efi | AlmaLinux-9-GenericCloud-latest.x86_64.qcow2 | CHECKSUM | almalinux.ini:22-27 |
almalinux-cloud-9.aarch64 | aarch64 | efi | AlmaLinux-9-GenericCloud-latest.aarch64.qcow2 | CHECKSUM | almalinux.ini:29-34 |
almalinux-cloud-10.x86_64 | x86_64 | efi | AlmaLinux-10-GenericCloud-latest.x86_64.qcow2 | CHECKSUM | almalinux.ini:36-41 |
almalinux-cloud-10.aarch64 | aarch64 | efi | AlmaLinux-10-GenericCloud-latest.aarch64.qcow2 | CHECKSUM | almalinux.ini:43-48 |
centos-cloud-9.x86_64 | x86_64 | bios | CentOS-Stream-GenericCloud-9-latest.x86_64.qcow2 | CentOS-Stream-GenericCloud-9-latest.x86_64.qcow2.SHA256SUM | centos.ini:8-13 |
centos-cloud-9.aarch64 | aarch64 | efi | CentOS-Stream-GenericCloud-9-latest.aarch64.qcow2 | CentOS-Stream-GenericCloud-9-latest.aarch64.qcow2.SHA256SUM | centos.ini:15-20 |
centos-cloud-10.x86_64 | x86_64 | bios | CentOS-Stream-GenericCloud-10-latest.x86_64.qcow2 | CentOS-Stream-GenericCloud-10-latest.x86_64.qcow2.SHA256SUM | centos.ini:22-27 |
centos-cloud-10.aarch64 | aarch64 | efi | CentOS-Stream-GenericCloud-10-latest.aarch64.qcow2 | CentOS-Stream-GenericCloud-10-latest.aarch64.qcow2.SHA256SUM | centos.ini:29-34 |
oracle-cloud-7.x86_64 | x86_64 | bios | OL7U9_x86_64-kvm-b257.qcow2 | SHA256SUM= 9e68a8fb682f… | oracle.ini:10-15 |
oracle-cloud-8.x86_64 | x86_64 | bios | OL8U10_x86_64-kvm-b287.qcow2 | SHA256SUM= cf9eb243b739… | oracle.ini:17-22 |
oracle-cloud-8.aarch64 | aarch64 | efi | OL8U10_aarch64-kvm-cloud-b170.qcow2 | SHA256SUM= 729114abf775… | oracle.ini:24-29 |
oracle-cloud-9.x86_64 | x86_64 | bios | OL9U8_x86_64-kvm-b293.qcow2 | SHA256SUM= b12103391327… | oracle.ini:31-36 |
oracle-cloud-9.aarch64 | aarch64 | efi | OL9U8_aarch64-kvm-cloud-b182.qcow2 | SHA256SUM= 4793c3ec49d9… | oracle.ini:38-43 |
oracle-cloud-10.x86_64 | x86_64 | efi | OL10U1_x86_64-kvm-b291.qcow2 | SHA256SUM= 8e59326c4bf7… | oracle.ini:45-50 |
oracle-cloud-10.aarch64 | aarch64 | efi | OL10U1_aarch64-kvm-cloud-b178.qcow2 | SHA256SUM= e203063e0e8b… | oracle.ini:52-57 |
rocky-cloud-8.x86_64 | x86_64 | efi | Rocky-8-GenericCloud-Base.latest.x86_64.qcow2 | CHECKSUM | rocky.ini:8-13 |
rocky-cloud-8.aarch64 | aarch64 | efi | Rocky-8-GenericCloud-Base.latest.aarch64.qcow2 | CHECKSUM | rocky.ini:15-20 |
rocky-cloud-9.x86_64 | x86_64 | efi | Rocky-9-GenericCloud-Base.latest.x86_64.qcow2 | CHECKSUM | rocky.ini:22-27 |
rocky-cloud-9.aarch64 | aarch64 | efi | Rocky-9-GenericCloud-Base.latest.aarch64.qcow2 | CHECKSUM | rocky.ini:29-34 |
rocky-cloud-10.x86_64 | x86_64 | efi | Rocky-10-GenericCloud-Base.latest.x86_64.qcow2 | CHECKSUM | rocky.ini:36-41 |
rocky-cloud-10.aarch64 | aarch64 | efi | Rocky-10-GenericCloud-Base.latest.aarch64.qcow2 | CHECKSUM | rocky.ini:43-48 |
Per distribution
| Group | User / password | Image directory | Checksum | Releases | aarch64 firmware |
|---|---|---|---|---|---|
almalinux | almalinux/almalinux | https://repo.almalinux.org/almalinux/R/cloud/ARCH/images/ | CHECKSUM on raw.repo.almalinux.org, HASH NAME lines | 8, 9, 10 | 8: Fedora's EDK2 |
centos | centos/centos | https://cloud.centos.org/centos/R-stream/ARCH/images/ | IMAGE.SHA256SUM per image, tag lines | 9, 10 | host EDK2 |
oracle | oracle/oracle | https://yum.oracle.com/templates/OracleLinux/OLR/uN/ARCH/ | literal SHA256SUM= in the INI | 7 (x86_64 only), 8, 9, 10 | 8: Fedora's EDK2 |
rocky | rocky/rocky | https://dl.rockylinux.org/pub/rocky/R/images/ARCH/ | CHECKSUM, tag lines | 8, 9, 10 | 8: Fedora's EDK2 |
- Every system also has
root/root; the group user has passwordless sudo (mk/010-qemu.mk:200-211). Host names areGROUP-RELEASE, asrocky-9(mk/010-qemu.mk:94-97). - Boot:
bioson x86_64 for CentOS 9 and 10 and Oracle 7, 8 and 9;efieverywhere else (sys-boot). - Fedora's EDK2 for
almalinux-cloud-8,oracle-cloud-8androcky-cloud-8on aarch64:GARDEN_AARCH64_FEDORA_EDK2_SYSTEMS(mk/010-qemu-aarch64.mk:134-145). - pkgproxy: the
snapsetup script andGOPROXYonly; dnf and yum are not proxied (mk/010-qemu.mk:127-180). - Downloads are cached in
$GARDEN_DL_DIR/GROUP/under the image's own file name, the checksum list beside it asFILE.sha256sums(rt-cache). Alatestfile stays until it is removed. - Release 10 on x86_64 needs an x86-64-v3 CPU;
QEMU_CPU_X86_64defaults tomax(README.md:681).
Roads from here
SYSTEMS · distributions
- Fedora cloud images — Fedora, where this family's packages start out
- Amazon Linux 2 and 2023 — Amazon Linux, Amazon's own distribution, with its URL program and quirks
- The support matrix — every family and architecture side by side
ARCHITECTURES · machines and firmware
- Boot types — what Boot=bios changes in the rules and the .run script
- UEFI firmware per system — Fedora's EDK2 for the aarch64 8s and where it comes from
RUNTIME · make rules and the CLI
- Downloading and checking images — how CHECKSUM lists and literal hashes are checked
FIRST BOOT · cloud-init changes
- The users every system gets — the root and group users and their passwords