Fedora cloud images
38 to 45, four arches for users
image-garden has Fedora 38 to 45 on x86_64 and aarch64, and 42 to 45 on riscv64 and s390x too, from Fedora's current, archive, RISC-V and secondary trees, each checked against Fedora's own checksum file; guests get a fedora user, SELinux as Fedora ships it, and no dnf cache.
On the map: systems
▶ Watch this deck — 6 scenes, ~5 min
Worth seeing first
- The support matrix — where Fedora sits among the other families
01 Every Fedora since 38
26 systems: Fedora 38 to 45. A system is named fedora-cloud-RELEASE.ARCH, such as fedora-cloud-42.x86_64.
Say your tool has to work on Fedora too. Fedora moves fast: a new release about every six months, each one supported for about thirteen, so the one your users run may already be in the archive. image-garden keeps eight of them, Fedora 38 to 45: twenty-six systems across their architectures. Ubuntu's running example is ubuntu-cloud-24.04.x86_64; here it's fedora-cloud-42.x86_64: the group fedora, the variant cloud, release 42, then the architecture. This deck shows where the images come from, which architectures they reach, what the first boot gives you, and what's worth knowing before you test on Fedora.
Details and sources
Details
data/fedora.inistarts with[META]:Group=fedora,Variant=cloud(fedora.ini:4-6), then 26 sections: releases 38 to 45 on x86_64 and aarch64, and 42 to 45 on riscv64 and s390x.- The running example of this deck,
[fedora-cloud-42.x86_64](fedora.ini:64-69). The section name is the system name; rulegen.py readsArch,BootandReleasefrom it (rulegen.py:114-127). - The README's Fedora entry: versions 38 to 45; x86_64 and aarch64 for all, riscv64 and s390x from 42 (README.md:643-649).
- A new release about every six months, each supported for about thirteen: Fedora's release cycle (derived, not in the source).
Read more
- The support matrix, system names, Ubuntu cloud images for the running example.
02 Where the images come from
Supported releases come from download.fedoraproject.org, end-of-life ones from dl.fedoraproject.org/pub/archive, RISC-V builds from pub/alt/risc-v and s390x from fedora-secondary. Each is checked against Fedora's CHECKSUM list, or a .sha256 file for riscv64.
Fedora keeps its images in more than one tree, and image-garden follows them. The newest releases, 43 to 45, sit in its main download tree. When a release reaches its end of life, Fedora moves it to the archive, and image-garden's URLs move with it: 38 to 42 point there already. RISC-V images come from a separate tree for alternative architectures, as dated builds, and s390x from the secondary one. Every image is checked before it's used. On x86_64, aarch64 and s390x, the checksum comes from Fedora's CHECKSUM file for that release and architecture, one line per image. A RISC-V image has a small .sha256 file of its own, right beside it.
Details and sources
Details
- Releases 43 to 45 on x86_64 and aarch64 use
https://download.fedoraproject.org/pub/fedora/linux/releases/R/Cloud/ARCH/images/(fedora.ini:93-105); 38 to 42 usehttps://dl.fedoraproject.org/pub/archive/fedora/linux/releases/R/…(fedora.ini:8-76). - The release notes record the moves: 39 and 40 "are no longer available at the primary download location" (NEWS:359-361); 41 and 42 "were moved there from the main download tree" (NEWS:204-205).
- riscv64 images are dated builds under
https://dl.fedoraproject.org/pub/alt/risc-v/release/R/Cloud/riscv64/images/, such asFedora-Cloud-Base-Generic-43-20260109.0.riscv64.qcow2, each withSHA256SUMS=pointing at the image URL plus.sha256(fedora.ini:78-85, fedora.ini:107-112). - s390x: 42 from
https://dl.fedoraproject.org/pub/archive/fedora-secondary/…(fedora.ini:87-91), 43 to 45 fromhttps://download.fedoraproject.org/pub/fedora-secondary/…(fedora.ini:114-118). - The x86_64, aarch64 and s390x sections set
SHA256SUMS=to Fedora'sFedora-Cloud-R-BUILD-ARCH-CHECKSUMfile; rulegen.py turns that key into adownload-with-sha256sumscall (rulegen.py:496-517). The helper reads bothHASH NAMElines and BSD tag lines,SHA256 (NAME) = HASH(image-garden:75-92). - The two lines on the slide were fetched on 21 November 2026: Fedora's CHECKSUM file uses the tag format and is PGP-signed (image-garden reads the hash lines and does not check the signature); the riscv64
.sha256file holds oneHASH NAMEline. download.fedoraproject.orgis Fedora's mirror redirector anddl.fedoraproject.orgits master server (derived, not in the source).
03 Two architectures for all, four from 42
x86_64 and aarch64 for 38 to 45; riscv64 and s390x for 42 to 45. efi on three architectures, platform on s390x. fedora-cloud-38.aarch64 boots with Fedora's EDK2.
Every Fedora release here runs on x86_64 and aarch64. From 42 on, Fedora also reaches 64-bit RISC-V and s390x, which puts it second only to Ubuntu in how many architectures it covers. How a system boots depends on the column. On x86_64, aarch64 and riscv64 it starts with UEFI firmware; on s390x there's no firmware file at all, and the system starts the platform's own way. One system needs other firmware: fedora-cloud-38 on aarch64 boots with Fedora's own EDK2, because its boot loader is older than what newer EDK2 enforces. On an x86 or Arm host, riscv64 and s390x are emulated, so expect minutes, not seconds, per boot.
Details and sources
Details
- Every release has
.x86_64and.aarch64sections;.riscv64and.s390xsections exist for 42, 43, 44 and 45 (data/fedora.ini). Only Ubuntu, with five, covers more architectures (the support matrix). - x86_64, aarch64 and riscv64 sections say
Boot=efi; s390x sections have noBoot, which s390x accepts asplatform, its only way (rulegen.py:300-333, fedora.ini:87-91). fedora-cloud-38is inGARDEN_AARCH64_FEDORA_EDK2_SYSTEMS, the aarch64 systems "whose shim or grub predate what newer EDK2 enforces" (mk/010-qemu-aarch64.mk:114-145). The other Fedora releases use the host's EDK2.- image-garden's own CI runs the four riscv64 and the four s390x systems emulated on x86_64, boot only; the riscv64 job's comment gives 20.4 minutes for the four on one machine and up to 9.1 minutes for one on another (.gitlab-ci.yml:922-958).
Read more
04 What the first boot gives you
Users root/root and fedora/fedora with passwordless sudo; host name fedora-42. pkgproxy covers snapd and Go modules here, not dnf.
Fedora has no quirk file of its own, so its first boot is the common one. You get two users: root, with password root, and fedora, with password fedora, sudo and no password asked. The machine calls itself fedora-42. What pkgproxy can do here is narrower than on Ubuntu. image-garden runs pkgproxy's apt script on Debian and Ubuntu only, and there's no script for dnf, so the packages your tests install come straight from Fedora's mirrors, every time. Two things do go through pkgproxy: snapd, if you install it later, and Go modules, through GOPROXY in /etc/environment.
Details and sources
Details
- There is no
mk/050-fedora.mk: noFEDORA_…_CLOUD_INIT_USER_DATA_TEMPLATEis defined, so the picker falls back to the commonCLOUD_INIT_USER_DATA_TEMPLATE(mk/010-qemu.mk:285-298). - rulegen.py passes the group as the template's second argument, the user's name (rulegen.py:467); the template makes
root/rootandfedora/fedorain groupuserswithsudo: ["ALL=(ALL) NOPASSWD:ALL"](mk/010-qemu.mk:200-211). - The host name is the group and release with dots and pluses turned into dashes,
fedora-42(mk/010-qemu.mk:94-97). - With a pkgproxy, the apt script runs only for groups
debianandubuntu, the snap script for every group butalpine(mk/010-qemu.mk:127-130, proxy/README.md:169-180). The snap script's drop-in also applies to a snapd installed later.GOPROXYgoes into/etc/environment(mk/010-qemu.mk:170-180). No script configures dnf. - The common template's
httpstohttprewrite runs only where/etc/aptexists (mk/010-qemu.mk:244): nothing happens on Fedora.
05 Worth knowing before you test
SELinux stays enforcing; packages arrive early; archived releases are frozen; riscv64 URLs name dated builds that may move.
A few things catch people out on Fedora. SELinux is enforcing, as Fedora ships it, and image-garden leaves it that way: a test that puts files where a confined service reads them may meet a denial you wouldn't see on Ubuntu. Fedora's packages are newer than most, so this is often where a new compiler warning or library change shows up first. Archived releases get no more updates, so what you test there is frozen. And the RISC-V images are dated builds from the alternative tree; image-garden itself notes that their URL doesn't look particularly stable, so they're the likeliest to need a refresh.
Details and sources
Details
- SELinux: nothing in image-garden's tree mentions SELinux, so the guest keeps the mode the image ships with. Fedora Cloud images ship SELinux in enforcing mode (derived, not in the source).
- New package versions: Fedora's practice of shipping recent upstream releases (derived).
- Archived releases: 38 to 42 come from
pub/archive(fedora.ini:8-91); a release in Fedora's archive has reached its end of life and gets no updates (derived). - The comment above the first riscv64 section: "XXX: This URL doesn't look particularly stable. The URL is from https://fedoraproject.org/wiki/Architectures/RISC-V/QEMU" (fedora.ini:78-85). The 42 build was refreshed once already (NEWS:136-137).
06 Where to go from here
Next: Enterprise Linux, the six architectures, UEFI firmware, the users, pkgproxy's user-data, downloads and the support matrix.
So Fedora is one file, eight releases, four architectures, and a first boot with a fedora user and no dnf cache. From here, the Enterprise Linux deck covers Fedora's relatives: AlmaLinux, CentOS Stream, Oracle Linux and Rocky Linux. The architecture deck shows the RISC-V and s390x machines, and the firmware deck explains Fedora's EDK2 on Arm. The users deck has the details of root and fedora, the pkgproxy deck shows what it adds to user-data, and the download deck how the checksum file is used. The support matrix sets Fedora beside every other family.
Details and sources
Read more
Basis of the statements on this page
The table is generated from data/fedora.ini of image-garden at the commit in garden.commit ("code"). The users, host name and pkgproxy coverage are read in mk/010-qemu.mk and rulegen.py ("code"). The checksum file formats were seen by fetching one file of each kind on 21 November 2026 ("run"). Fedora's release cycle, its trees and SELinux's mode in the images are Fedora's practice ("derived").
Every Fedora system
The system name is fedora-cloud-RELEASE.ARCH. Boot platform means no firmware file (s390x). The checksum column names the checksum file, in the same directory as the image.
| System | Arch | Boot | Tree | Image file | Checksum source | Section |
|---|---|---|---|---|---|---|
fedora-cloud-38.x86_64 | x86_64 | efi | archive | Fedora-Cloud-Base-38-1.6.x86_64.qcow2 | Fedora-Cloud-38-1.6-x86_64-CHECKSUM | fedora.ini:8-13 |
fedora-cloud-38.aarch64 | aarch64 | efi | archive | Fedora-Cloud-Base-38-1.6.aarch64.qcow2 | Fedora-Cloud-38-1.6-aarch64-CHECKSUM | fedora.ini:15-20 |
fedora-cloud-39.x86_64 | x86_64 | efi | archive | Fedora-Cloud-Base-39-1.5.x86_64.qcow2 | Fedora-Cloud-39-1.5-x86_64-CHECKSUM | fedora.ini:22-27 |
fedora-cloud-39.aarch64 | aarch64 | efi | archive | Fedora-Cloud-Base-39-1.5.aarch64.qcow2 | Fedora-Cloud-39-1.5-aarch64-CHECKSUM | fedora.ini:29-34 |
fedora-cloud-40.x86_64 | x86_64 | efi | archive | Fedora-Cloud-Base-Generic.x86_64-40-1.14.qcow2 | Fedora-Cloud-40-1.14-x86_64-CHECKSUM | fedora.ini:36-41 |
fedora-cloud-40.aarch64 | aarch64 | efi | archive | Fedora-Cloud-Base-Generic.aarch64-40-1.14.qcow2 | Fedora-Cloud-40-1.14-aarch64-CHECKSUM | fedora.ini:43-48 |
fedora-cloud-41.x86_64 | x86_64 | efi | archive | Fedora-Cloud-Base-Generic-41-1.4.x86_64.qcow2 | Fedora-Cloud-41-1.4-x86_64-CHECKSUM | fedora.ini:50-55 |
fedora-cloud-41.aarch64 | aarch64 | efi | archive | Fedora-Cloud-Base-Generic-41-1.4.aarch64.qcow2 | Fedora-Cloud-41-1.4-aarch64-CHECKSUM | fedora.ini:57-62 |
fedora-cloud-42.x86_64 | x86_64 | efi | archive | Fedora-Cloud-Base-Generic-42-1.1.x86_64.qcow2 | Fedora-Cloud-42-1.1-x86_64-CHECKSUM | fedora.ini:64-69 |
fedora-cloud-42.aarch64 | aarch64 | efi | archive | Fedora-Cloud-Base-Generic-42-1.1.aarch64.qcow2 | Fedora-Cloud-42-1.1-aarch64-CHECKSUM | fedora.ini:71-76 |
fedora-cloud-42.riscv64 | riscv64 | efi | alt/risc-v | Fedora-Cloud-Base-Generic-42.20250911-2251ba41cdd3.riscv64.qcow2 | Fedora-Cloud-Base-Generic-42.20250911-2251ba41cdd3.riscv64.qcow2.sha256 | fedora.ini:80-85 |
fedora-cloud-42.s390x | s390x | platform | archive, secondary | Fedora-Cloud-Base-Generic-42-1.1.s390x.qcow2 | Fedora-Cloud-42-1.1-s390x-CHECKSUM | fedora.ini:87-91 |
fedora-cloud-43.x86_64 | x86_64 | efi | current | Fedora-Cloud-Base-Generic-43-1.6.x86_64.qcow2 | Fedora-Cloud-43-1.6-x86_64-CHECKSUM | fedora.ini:93-98 |
fedora-cloud-43.aarch64 | aarch64 | efi | current | Fedora-Cloud-Base-Generic-43-1.6.aarch64.qcow2 | Fedora-Cloud-43-1.6-aarch64-CHECKSUM | fedora.ini:100-105 |
fedora-cloud-43.riscv64 | riscv64 | efi | alt/risc-v | Fedora-Cloud-Base-Generic-43-20260109.0.riscv64.qcow2 | Fedora-Cloud-Base-Generic-43-20260109.0.riscv64.qcow2.sha256 | fedora.ini:107-112 |
fedora-cloud-43.s390x | s390x | platform | secondary | Fedora-Cloud-Base-Generic-43-1.6.s390x.qcow2 | Fedora-Cloud-43-1.6-s390x-CHECKSUM | fedora.ini:114-118 |
fedora-cloud-44.x86_64 | x86_64 | efi | current | Fedora-Cloud-Base-Generic-44-1.7.x86_64.qcow2 | Fedora-Cloud-44-1.7-x86_64-CHECKSUM | fedora.ini:120-125 |
fedora-cloud-44.aarch64 | aarch64 | efi | current | Fedora-Cloud-Base-Generic-44-1.7.aarch64.qcow2 | Fedora-Cloud-44-1.7-aarch64-CHECKSUM | fedora.ini:127-132 |
fedora-cloud-44.riscv64 | riscv64 | efi | alt/risc-v | Fedora-Cloud-Base-Generic-44-20260604.0.riscv64.qcow2 | Fedora-Cloud-Base-Generic-44-20260604.0.riscv64.qcow2.sha256 | fedora.ini:134-139 |
fedora-cloud-44.s390x | s390x | platform | secondary | Fedora-Cloud-Base-Generic-44-1.7.s390x.qcow2 | Fedora-Cloud-44-1.7-s390x-CHECKSUM | fedora.ini:141-145 |
fedora-cloud-45.x86_64 | x86_64 | efi | current | Fedora-Cloud-Base-Generic-45-1.4.x86_64.qcow2 | Fedora-Cloud-45-1.4-x86_64-CHECKSUM | fedora.ini:147-152 |
fedora-cloud-45.aarch64 | aarch64 | efi | current | Fedora-Cloud-Base-Generic-45-1.4.aarch64.qcow2 | Fedora-Cloud-45-1.4-aarch64-CHECKSUM | fedora.ini:154-159 |
fedora-cloud-45.riscv64 | riscv64 | efi | alt/risc-v | Fedora-Cloud-Base-Generic-45-20261022.0.riscv64.qcow2 | Fedora-Cloud-Base-Generic-45-20261022.0.riscv64.qcow2.sha256 | fedora.ini:161-166 |
fedora-cloud-45.s390x | s390x | platform | secondary | Fedora-Cloud-Base-Generic-45-1.4.s390x.qcow2 | Fedora-Cloud-45-1.4-s390x-CHECKSUM | fedora.ini:168-172 |
URL patterns
| Tree | Releases | URL directory |
|---|---|---|
| current | 43 to 45, x86_64 and aarch64 | https://download.fedoraproject.org/pub/fedora/linux/releases/R/Cloud/ARCH/images/ |
| archive | 38 to 42, x86_64 and aarch64 | https://dl.fedoraproject.org/pub/archive/fedora/linux/releases/R/Cloud/ARCH/images/ |
| alt/risc-v | 42 to 45, riscv64 | https://dl.fedoraproject.org/pub/alt/risc-v/release/R/Cloud/riscv64/images/ |
| archive, secondary | 42, s390x | https://dl.fedoraproject.org/pub/archive/fedora-secondary/releases/42/Cloud/s390x/images/ |
| secondary | 43 to 45, s390x | https://download.fedoraproject.org/pub/fedora-secondary/releases/R/Cloud/s390x/images/ |
- Checksums:
Fedora-Cloud-R-BUILD-ARCH-CHECKSUM(tag lines,SHA256 (NAME) = HASH, PGP-signed; the signature is not checked) beside x86_64, aarch64 and s390x images;IMAGE.qcow2.sha256(HASH NAME) beside riscv64 images. Both are read bydownload-with-sha256sums(image-garden:75-92, rulegen.py:496-517). - Downloads are cached in
$GARDEN_DL_DIR/fedora/under the image's own file name, with a link named after the system (rt-cache).
First boot
- Users:
root/rootandfedora/fedora, the latter with passwordless sudo (mk/010-qemu.mk:200-211, rulegen.py:467).--queryprints both assystem.users.0andsystem.users.1(mk/010-qemu.mk:79-88). - Host name:
fedora-R, asfedora-42(mk/010-qemu.mk:94-97). - Template: the common one; Fedora has no quirk file (mk/010-qemu.mk:285-298).
- pkgproxy: the
snapsetup script andGOPROXYin/etc/environment; no apt script (Debian and Ubuntu only) and no dnf script (mk/010-qemu.mk:127-180). The image download itself can still come through a pkgproxy on the host (px-downloads).
Firmware and machines
- x86_64:
q35,-cpu max, OVMF from the host or the snap (sys-firmware). - aarch64:
virt,-cpu max;fedora-cloud-38uses Fedora's EDK2 fromGARDEN_AARCH64_FEDORA_EDK2_SYSTEMS(mk/010-qemu-aarch64.mk:134-145). - riscv64:
virt,acpi=off, EDK2; s390x:s390-ccw-virtio, no firmware files (sys-arches).
Roads from here
SYSTEMS · distributions
- AlmaLinux, CentOS Stream, Oracle Linux and Rocky Linux — AlmaLinux, CentOS Stream, Oracle Linux and Rocky Linux, Fedora's enterprise relatives
- The support matrix — every family and architecture side by side
ARCHITECTURES · machines and firmware
- Six architectures, six QEMU machines — the riscv64 and s390x machines Fedora also runs on
- UEFI firmware per system — why fedora-cloud-38 on aarch64 boots with Fedora's own EDK2
RUNTIME · make rules and the CLI
- Downloading and checking images — how the checksum file is fetched, read and trusted
FIRST BOOT · cloud-init changes
- The users every system gets — the root and fedora users, their passwords and sudo
PKGPROXY · caching for guests
- What pkgproxy adds to user-data — what pkgproxy adds to a guest's user-data, and for which families