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

01 Four distributions, one family

ENTERPRISE LINUX RHEL itself needs a subscription, so you test on its rebuilds and relatives AlmaLinux 8 9 10 CentOS Stream 9 10 Oracle Linux 7 8 9 10 Rocky Linux 8 9 10 group almalinux group centos group oracle group rocky rocky-cloud-9.x86_64 oracle-cloud-7.x86_64 23 systems releases 7 to 10 x86_64 and aarch64 sources releases boot first boot worth knowing
Four distributions of the Red Hat family, each a group of its own: AlmaLinux 8 to 10, CentOS Stream 9 and 10, Oracle Linux 7 to 10, Rocky Linux 8 to 10; systems are named like rocky-cloud-9.x86_64 and oracle-cloud-7.x86_64, 23 in all on x86_64 and aarch64; the deck covers sources, releases, boot, first boot and what is worth knowing

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) and Group=rocky (rocky.ini:4-6), all Variant=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).

02 Four sources, three ways to check

FOUR SOURCES image file checksum from AlmaLinux AlmaLinux-9-GenericCloud-latest.x86_64.qcow2 CentOS Stream CentOS-Stream-GenericCloud-9-latest.x86_64.qcow2 Rocky Linux Rocky-9-GenericCloud-Base.latest.x86_64.qcow2 the build fetched first stays until you clear the cache CHECKSUM list CHECKSUM list IMAGE.SHA256SUM Oracle Linux OL7U9_x86_64-kvm-b257.qcow2 a fixed build; Oracle lists checksums on a web page image-garden itself oracle-cloud-7.x86_64 https://yum.oracle.com/templates/OracleLinux/OL7/u9/x86_64/… sha256 9e68a8fb682f7e30b6b2475e719af8801cf24b43…
AlmaLinux, CentOS and Rocky name their newest build with latest; image-garden keeps the build it fetched first until the cache is cleared; AlmaLinux and Rocky are checked against a CHECKSUM list per directory, CentOS against a .SHA256SUM file per image; Oracle's fixed builds, such as OL7U9_x86_64-kvm-b257.qcow2, have their SHA-256 hash written into image-garden itself

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 against https://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 against CHECKSUM in the same directory (rocky.ini:8-48).
  • Oracle Linux: fixed template builds under https://yum.oracle.com/templates/OracleLinux/OLR/uN/ARCH/, such as OL7U9_x86_64-kvm-b257.qcow2, each with a literal SHA256SUM=; the file's comment points at Oracle's templates page (oracle.ini:8-57). The hashes were added by hand (NEWS:510).
  • SHA256SUMS= becomes download-with-sha256sums, SHA256SUM= becomes download-with-sha256sum with the hash on the command line (rulegen.py:62-71, rulegen.py:496-517). The list is fetched once and kept as FILE.sha256sums beside the image; an image already in the cache that matches it is not fetched again (image-garden:460-559).
  • The .url rule depends only on the makefiles, and the cached latest file keeps its name, so a newer build is fetched only after the cached file is removed, for example by image-garden make distclean (rulegen.py:520-524, derived from the rules).
  • Formats seen on 21 November 2026: AlmaLinux's CHECKSUM has HASH NAME lines, Rocky's and CentOS's files SHA256 (NAME) = HASH lines; 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

RELEASES AND ARCHITECTURES 7 8 9 10 AlmaLinux CentOS Stream Oracle Linux Rocky Linux both both both both both both both both x86_64 only both both both both: x86_64 and aarch64, and nothing else: no riscv64, s390x or ppc64 the other architecture is emulated: aarch64 on an x86 laptop, x86_64 on an Arm machine one of each release, on both: AlmaLinux or Rocky Linux, 8 to 10
A grid of the four distributions by release 7 to 10: AlmaLinux and Rocky Linux 8, 9 and 10, CentOS Stream 9 and 10, Oracle Linux 7 on x86_64 only and 8 to 10 on both; every system is on x86_64 and aarch64 and nothing else; the other architecture is emulated; AlmaLinux or Rocky covers 8 to 10 on both

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

04 Which firmware starts them

FIRMWARE x86_64 aarch64 centos-cloud-9 centos-cloud-10 oracle-cloud-7 oracle-cloud-8 oracle-cloud-9 BIOS the other seven: UEFI CentOS images: no EFI system partition .run: no .efi-code, no .efi-vars QEMU's own BIOS starts it all efi; the 8s are the odd ones out almalinux-cloud-8 oracle-cloud-8 rocky-cloud-8 shim or grub older than newer EDK2 allows Fedora's EDK2 the snap: its qemu-aarch64 component elsewhere: downloaded by checksum
On x86_64, centos-cloud-9 and 10 and oracle-cloud-7, 8 and 9 boot with a BIOS, since the CentOS images have no EFI system partition; their .run script has no firmware files and QEMU's own BIOS starts them; the rest use efi. On aarch64 all use efi, and almalinux-cloud-8, oracle-cloud-8 and rocky-cloud-8 boot with Fedora's EDK2, from the snap or downloaded by checksum

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=bios on x86_64: centos-cloud-9 and centos-cloud-10 (centos.ini:8-27), oracle-cloud-7, -8 and -9 (oracle.ini:10-36). Every other x86_64 section of the four files, and every aarch64 one, says Boot=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 .run script 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-8 and rocky-cloud-8 are in GARDEN_AARCH64_FEDORA_EDK2_SYSTEMS, with Fedora's EDK2 from the snap's qemu-aarch64 component or downloaded by checksum from image-garden's package registry (mk/010-qemu-aarch64.mk:114-167).

05 A user named after the group

THE FIRST BOOT the image's own default user: replaced by image-garden's list users: - name: root plain_text_passwd: root - name: GROUP plain_text_passwd: GROUP sudo: ["ALL=(ALL) NOPASSWD:ALL"] system you log in as rocky-cloud-9 rocky oracle-cloud-7 oracle centos-cloud-10 centos almalinux-cloud-10 almalinux $ ./rocky-cloud-9.x86_64.run --query vm.memory_mb=2048 system.users.0.username=root system.users.1.username=rocky hostname: rocky-9 dnf, yum not cached by pkgproxy snap, go through pkgproxy
image-garden's user-data lists its own users instead of the image's default user: root with password root and a user named after the group with the same password and passwordless sudo; rocky-cloud-9 logs in as rocky, oracle-cloud-7 as oracle, centos-cloud-10 as centos; the .run script's --query prints both users; the host name is rocky-9; pkgproxy does not cache dnf or yum, only snapd and Go modules

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/root and GROUP/GROUP with sudo: ["ALL=(ALL) NOPASSWD:ALL"] (mk/010-qemu.mk:200-211). None of the four groups has a quirk template.
  • --query prints vm.memory_mb and the two users, root and the group (mk/010-qemu.mk:57-90, rulegen.py:596).
  • The host name is GROUP-RELEASE, as rocky-9 (mk/010-qemu.mk:94-97).
  • With a pkgproxy, these groups get the snap setup script and GOPROXY, 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, rocky or almalinux) come from their cloud-init configuration; a users: list without default replaces that user (derived, cloud-init behaviour).

06 Worth knowing before you test

WORTH KNOWING EL 10: x86-64-v3 Haswell or newer; the default -cpu max passes your host's CPU through $ image-garden make QEMU_CPU_X86_64=Haswell rocky-cloud-10.x86_64.run SELinux enforcing as these distributions ship it CentOS Stream Fedora CentOS Stream RHEL Alma, Rocky, Oracle the next RHEL minor release is made in Stream: it runs ahead Oracle Linux 7 an older generation: a long-tail check, not a modern baseline
Four things worth knowing: release 10 of all four needs an x86-64-v3 CPU, which the default -cpu max passes through from a recent host, or set QEMU_CPU_X86_64=Haswell; SELinux is enforcing; CentOS Stream is where the next RHEL minor release is made, ahead of RHEL and its rebuilds; Oracle Linux 7 is old, a long-tail check

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=Haswell or newer if needed." (README.md:681); QEMU_CPU_X86_64 defaults to max (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 .run script 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.

07 Where to go from here

ROADS Enterprise Linux Fedora cloud images where the packages start Amazon Linux Amazon's own distribution Boot types what bios changes UEFI firmware Fedora's EDK2 on Arm The users root and the group user Download and verify lists and literal hashes The support matrix every family
Roads from the Enterprise Linux deck: Fedora, Amazon Linux, boot types, UEFI firmware, the users, downloading and checking, and the support matrix

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.

SystemArchBootImage fileChecksum sourceSection
almalinux-cloud-8.x86_64x86_64efiAlmaLinux-8-GenericCloud-latest.x86_64.qcow2CHECKSUMalmalinux.ini:8-13
almalinux-cloud-8.aarch64aarch64efiAlmaLinux-8-GenericCloud-latest.aarch64.qcow2CHECKSUMalmalinux.ini:15-20
almalinux-cloud-9.x86_64x86_64efiAlmaLinux-9-GenericCloud-latest.x86_64.qcow2CHECKSUMalmalinux.ini:22-27
almalinux-cloud-9.aarch64aarch64efiAlmaLinux-9-GenericCloud-latest.aarch64.qcow2CHECKSUMalmalinux.ini:29-34
almalinux-cloud-10.x86_64x86_64efiAlmaLinux-10-GenericCloud-latest.x86_64.qcow2CHECKSUMalmalinux.ini:36-41
almalinux-cloud-10.aarch64aarch64efiAlmaLinux-10-GenericCloud-latest.aarch64.qcow2CHECKSUMalmalinux.ini:43-48
centos-cloud-9.x86_64x86_64biosCentOS-Stream-GenericCloud-9-latest.x86_64.qcow2CentOS-Stream-GenericCloud-9-latest.x86_64.qcow2.SHA256SUMcentos.ini:8-13
centos-cloud-9.aarch64aarch64efiCentOS-Stream-GenericCloud-9-latest.aarch64.qcow2CentOS-Stream-GenericCloud-9-latest.aarch64.qcow2.SHA256SUMcentos.ini:15-20
centos-cloud-10.x86_64x86_64biosCentOS-Stream-GenericCloud-10-latest.x86_64.qcow2CentOS-Stream-GenericCloud-10-latest.x86_64.qcow2.SHA256SUMcentos.ini:22-27
centos-cloud-10.aarch64aarch64efiCentOS-Stream-GenericCloud-10-latest.aarch64.qcow2CentOS-Stream-GenericCloud-10-latest.aarch64.qcow2.SHA256SUMcentos.ini:29-34
oracle-cloud-7.x86_64x86_64biosOL7U9_x86_64-kvm-b257.qcow2SHA256SUM= 9e68a8fb682f…oracle.ini:10-15
oracle-cloud-8.x86_64x86_64biosOL8U10_x86_64-kvm-b287.qcow2SHA256SUM= cf9eb243b739…oracle.ini:17-22
oracle-cloud-8.aarch64aarch64efiOL8U10_aarch64-kvm-cloud-b170.qcow2SHA256SUM= 729114abf775…oracle.ini:24-29
oracle-cloud-9.x86_64x86_64biosOL9U8_x86_64-kvm-b293.qcow2SHA256SUM= b12103391327…oracle.ini:31-36
oracle-cloud-9.aarch64aarch64efiOL9U8_aarch64-kvm-cloud-b182.qcow2SHA256SUM= 4793c3ec49d9…oracle.ini:38-43
oracle-cloud-10.x86_64x86_64efiOL10U1_x86_64-kvm-b291.qcow2SHA256SUM= 8e59326c4bf7…oracle.ini:45-50
oracle-cloud-10.aarch64aarch64efiOL10U1_aarch64-kvm-cloud-b178.qcow2SHA256SUM= e203063e0e8b…oracle.ini:52-57
rocky-cloud-8.x86_64x86_64efiRocky-8-GenericCloud-Base.latest.x86_64.qcow2CHECKSUMrocky.ini:8-13
rocky-cloud-8.aarch64aarch64efiRocky-8-GenericCloud-Base.latest.aarch64.qcow2CHECKSUMrocky.ini:15-20
rocky-cloud-9.x86_64x86_64efiRocky-9-GenericCloud-Base.latest.x86_64.qcow2CHECKSUMrocky.ini:22-27
rocky-cloud-9.aarch64aarch64efiRocky-9-GenericCloud-Base.latest.aarch64.qcow2CHECKSUMrocky.ini:29-34
rocky-cloud-10.x86_64x86_64efiRocky-10-GenericCloud-Base.latest.x86_64.qcow2CHECKSUMrocky.ini:36-41
rocky-cloud-10.aarch64aarch64efiRocky-10-GenericCloud-Base.latest.aarch64.qcow2CHECKSUMrocky.ini:43-48

Per distribution

GroupUser / passwordImage directoryChecksumReleasesaarch64 firmware
almalinuxalmalinux/almalinuxhttps://repo.almalinux.org/almalinux/R/cloud/ARCH/images/CHECKSUM on raw.repo.almalinux.org, HASH NAME lines8, 9, 108: Fedora's EDK2
centoscentos/centoshttps://cloud.centos.org/centos/R-stream/ARCH/images/IMAGE.SHA256SUM per image, tag lines9, 10host EDK2
oracleoracle/oraclehttps://yum.oracle.com/templates/OracleLinux/OLR/uN/ARCH/literal SHA256SUM= in the INI7 (x86_64 only), 8, 9, 108: Fedora's EDK2
rockyrocky/rockyhttps://dl.rockylinux.org/pub/rocky/R/images/ARCH/CHECKSUM, tag lines8, 9, 108: Fedora's EDK2
  • Every system also has root/root; the group user has passwordless sudo (mk/010-qemu.mk:200-211). Host names are GROUP-RELEASE, as rocky-9 (mk/010-qemu.mk:94-97).
  • Boot: bios on x86_64 for CentOS 9 and 10 and Oracle 7, 8 and 9; efi everywhere else (sys-boot).
  • Fedora's EDK2 for almalinux-cloud-8, oracle-cloud-8 and rocky-cloud-8 on aarch64: GARDEN_AARCH64_FEDORA_EDK2_SYSTEMS (mk/010-qemu-aarch64.mk:134-145).
  • pkgproxy: the snap setup script and GOPROXY only; 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 as FILE.sha256sums (rt-cache). A latest file stays until it is removed.
  • Release 10 on x86_64 needs an x86-64-v3 CPU; QEMU_CPU_X86_64 defaults to max (README.md:681).

Roads from here

SYSTEMS · distributions

ARCHITECTURES · machines and firmware

RUNTIME · make rules and the CLI

FIRST BOOT · cloud-init changes