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

01 Every Fedora since 38

FEDORA CLOUD IMAGES a new release every six months: the one your users run may be in the archive 38 39 40 41 42 43 44 45 $ image-garden make list-systems \ | grep -c '^fedora-' 26 eight releases, 26 systems the running example fedora - cloud - 42 . x86_64 group variant release arch where they come from which architectures the first boot worth knowing
Fedora releases 38 to 45, 26 systems, as image-garden make list-systems counts them; the running example fedora-cloud-42.x86_64 is taken apart into group, variant, release and architecture; the deck covers where images come from, architectures, the first boot and what is worth knowing

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.ini starts 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 reads Arch, Boot and Release from 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

02 Where the images come from

FOUR TREES 43 to 45 download.fedoraproject.org/pub/fedora/linux/releases/R/Cloud/ARCH/images/ 38 to 42 dl.fedoraproject.org/pub/archive/fedora/linux/releases/R/Cloud/ARCH/images/ riscv64 dl.fedoraproject.org/pub/alt/risc-v/release/R/Cloud/riscv64/images/ s390x download.fedoraproject.org/pub/fedora-secondary/releases/R/Cloud/s390x/images/ 42 on s390x sits in the archive's copy of the secondary tree x86_64, aarch64, s390x: one CHECKSUM file per release and architecture SHA256 (Fedora-Cloud-Base-Generic-43-1.6.x86_64.qcow2) = 846574c8a97cd2d8… riscv64: a .sha256 file beside each image 8e76c043f243250d… Fedora-Cloud-Base-Generic-43-20260109.0.riscv64.qcow2
Four trees: releases 43 to 45 from download.fedoraproject.org, 38 to 42 from the archive on dl.fedoraproject.org, riscv64 dated builds from pub/alt/risc-v, s390x from fedora-secondary; each image is checked against a line of Fedora's CHECKSUM file, or, on riscv64, a .sha256 file beside the image

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 use https://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 as Fedora-Cloud-Base-Generic-43-20260109.0.riscv64.qcow2, each with SHA256SUMS= 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 from https://download.fedoraproject.org/pub/fedora-secondary/… (fedora.ini:114-118).
  • The x86_64, aarch64 and s390x sections set SHA256SUMS= to Fedora's Fedora-Cloud-R-BUILD-ARCH-CHECKSUM file; rulegen.py turns that key into a download-with-sha256sums call (rulegen.py:496-517). The helper reads both HASH NAME lines 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 .sha256 file holds one HASH NAME line.
  • download.fedoraproject.org is Fedora's mirror redirector and dl.fedoraproject.org its master server (derived, not in the source).

03 Two architectures for all, four from 42

FOUR ARCHITECTURES x86_64 aarch64 riscv64 s390x Fedora 38 Fedora 39 Fedora 40 Fedora 41 Fedora 42 Fedora 43 Fedora 44 Fedora 45 efi efi efi efi efi efi efi efi efi efi efi efi efi efi efi efi efi efi efi efi platform platform platform platform fedora-cloud-38.aarch64: Fedora's EDK2 on an x86 or Arm host, riscv64 and s390x are emulated: expect minutes per boot
A grid of Fedora 38 to 45 by architecture: x86_64 and aarch64 for every release, riscv64 and s390x from 42; efi on x86_64, aarch64 and riscv64, platform on s390x; fedora-cloud-38 on aarch64 boots with Fedora's EDK2; riscv64 and s390x are emulated on x86 and Arm hosts, minutes per boot

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_64 and .aarch64 sections; .riscv64 and .s390x sections 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 no Boot, which s390x accepts as platform, its only way (rulegen.py:300-333, fedora.ini:87-91).
  • fedora-cloud-38 is in GARDEN_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).

04 What the first boot gives you

THE FIRST BOOT the common template: no Fedora quirk file users: - name: root plain_text_passwd: root - name: fedora plain_text_passwd: fedora sudo: ["ALL=(ALL) NOPASSWD:ALL"] hostname: fedora-42 what pkgproxy sets up in the guest apt Debian and Ubuntu only dnf no script: straight from Fedora's mirrors snap snapd drop-in, also if installed later go GOPROXY in /etc/environment
Fedora gets the common user-data template: users root with password root and fedora with password fedora and passwordless sudo, host name fedora-42. pkgproxy's apt script runs on Debian and Ubuntu only and there is no dnf script, so dnf downloads come from Fedora's mirrors; snapd, if installed later, and Go modules through GOPROXY in /etc/environment do go through pkgproxy

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: no FEDORA_…_CLOUD_INIT_USER_DATA_TEMPLATE is defined, so the picker falls back to the common CLOUD_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/root and fedora/fedora in group users with sudo: ["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 debian and ubuntu, the snap script for every group but alpine (mk/010-qemu.mk:127-130, proxy/README.md:169-180). The snap script's drop-in also applies to a snapd installed later. GOPROXY goes into /etc/environment (mk/010-qemu.mk:170-180). No script configures dnf.
  • The common template's https to http rewrite runs only where /etc/apt exists (mk/010-qemu.mk:244): nothing happens on Fedora.

05 Worth knowing before you test

WORTH KNOWING SELinux enforcing as Fedora ships it; image-garden leaves it alone a confined service may deny what Ubuntu allows new packages early compiler and library changes often show up here first a good place to meet tomorrow's problems today archived releases 38 to 42 live in the archive: no more updates what you test there is frozen riscv64 dated builds from the alternative tree "This URL doesn't look particularly stable." image-garden's own note on fedora-cloud-42.riscv64
Four things worth knowing on Fedora: SELinux stays enforcing as Fedora ships it, so a confined service may deny access you would not see on Ubuntu; new package versions often arrive here first; archived releases get no updates; riscv64 images are dated builds whose URL image-garden's own note calls not particularly stable

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

ROADS Fedora cloud images Enterprise Linux Fedora's relatives Six architectures RISC-V and s390x machines UEFI firmware Fedora's EDK2 on Arm The users root and fedora pkgproxy's user-data what it adds, per family Download and verify the checksum file The support matrix every family
Roads from Fedora cloud images: Enterprise Linux, six architectures, UEFI firmware, the users, pkgproxy's user-data, downloading and checking, and the support matrix

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.

SystemArchBootTreeImage fileChecksum sourceSection
fedora-cloud-38.x86_64x86_64efiarchiveFedora-Cloud-Base-38-1.6.x86_64.qcow2Fedora-Cloud-38-1.6-x86_64-CHECKSUMfedora.ini:8-13
fedora-cloud-38.aarch64aarch64efiarchiveFedora-Cloud-Base-38-1.6.aarch64.qcow2Fedora-Cloud-38-1.6-aarch64-CHECKSUMfedora.ini:15-20
fedora-cloud-39.x86_64x86_64efiarchiveFedora-Cloud-Base-39-1.5.x86_64.qcow2Fedora-Cloud-39-1.5-x86_64-CHECKSUMfedora.ini:22-27
fedora-cloud-39.aarch64aarch64efiarchiveFedora-Cloud-Base-39-1.5.aarch64.qcow2Fedora-Cloud-39-1.5-aarch64-CHECKSUMfedora.ini:29-34
fedora-cloud-40.x86_64x86_64efiarchiveFedora-Cloud-Base-Generic.x86_64-40-1.14.qcow2Fedora-Cloud-40-1.14-x86_64-CHECKSUMfedora.ini:36-41
fedora-cloud-40.aarch64aarch64efiarchiveFedora-Cloud-Base-Generic.aarch64-40-1.14.qcow2Fedora-Cloud-40-1.14-aarch64-CHECKSUMfedora.ini:43-48
fedora-cloud-41.x86_64x86_64efiarchiveFedora-Cloud-Base-Generic-41-1.4.x86_64.qcow2Fedora-Cloud-41-1.4-x86_64-CHECKSUMfedora.ini:50-55
fedora-cloud-41.aarch64aarch64efiarchiveFedora-Cloud-Base-Generic-41-1.4.aarch64.qcow2Fedora-Cloud-41-1.4-aarch64-CHECKSUMfedora.ini:57-62
fedora-cloud-42.x86_64x86_64efiarchiveFedora-Cloud-Base-Generic-42-1.1.x86_64.qcow2Fedora-Cloud-42-1.1-x86_64-CHECKSUMfedora.ini:64-69
fedora-cloud-42.aarch64aarch64efiarchiveFedora-Cloud-Base-Generic-42-1.1.aarch64.qcow2Fedora-Cloud-42-1.1-aarch64-CHECKSUMfedora.ini:71-76
fedora-cloud-42.riscv64riscv64efialt/risc-vFedora-Cloud-Base-Generic-42.20250911-2251ba41cdd3.riscv64.qcow2Fedora-Cloud-Base-Generic-42.20250911-2251ba41cdd3.riscv64.qcow2.sha256fedora.ini:80-85
fedora-cloud-42.s390xs390xplatformarchive, secondaryFedora-Cloud-Base-Generic-42-1.1.s390x.qcow2Fedora-Cloud-42-1.1-s390x-CHECKSUMfedora.ini:87-91
fedora-cloud-43.x86_64x86_64eficurrentFedora-Cloud-Base-Generic-43-1.6.x86_64.qcow2Fedora-Cloud-43-1.6-x86_64-CHECKSUMfedora.ini:93-98
fedora-cloud-43.aarch64aarch64eficurrentFedora-Cloud-Base-Generic-43-1.6.aarch64.qcow2Fedora-Cloud-43-1.6-aarch64-CHECKSUMfedora.ini:100-105
fedora-cloud-43.riscv64riscv64efialt/risc-vFedora-Cloud-Base-Generic-43-20260109.0.riscv64.qcow2Fedora-Cloud-Base-Generic-43-20260109.0.riscv64.qcow2.sha256fedora.ini:107-112
fedora-cloud-43.s390xs390xplatformsecondaryFedora-Cloud-Base-Generic-43-1.6.s390x.qcow2Fedora-Cloud-43-1.6-s390x-CHECKSUMfedora.ini:114-118
fedora-cloud-44.x86_64x86_64eficurrentFedora-Cloud-Base-Generic-44-1.7.x86_64.qcow2Fedora-Cloud-44-1.7-x86_64-CHECKSUMfedora.ini:120-125
fedora-cloud-44.aarch64aarch64eficurrentFedora-Cloud-Base-Generic-44-1.7.aarch64.qcow2Fedora-Cloud-44-1.7-aarch64-CHECKSUMfedora.ini:127-132
fedora-cloud-44.riscv64riscv64efialt/risc-vFedora-Cloud-Base-Generic-44-20260604.0.riscv64.qcow2Fedora-Cloud-Base-Generic-44-20260604.0.riscv64.qcow2.sha256fedora.ini:134-139
fedora-cloud-44.s390xs390xplatformsecondaryFedora-Cloud-Base-Generic-44-1.7.s390x.qcow2Fedora-Cloud-44-1.7-s390x-CHECKSUMfedora.ini:141-145
fedora-cloud-45.x86_64x86_64eficurrentFedora-Cloud-Base-Generic-45-1.4.x86_64.qcow2Fedora-Cloud-45-1.4-x86_64-CHECKSUMfedora.ini:147-152
fedora-cloud-45.aarch64aarch64eficurrentFedora-Cloud-Base-Generic-45-1.4.aarch64.qcow2Fedora-Cloud-45-1.4-aarch64-CHECKSUMfedora.ini:154-159
fedora-cloud-45.riscv64riscv64efialt/risc-vFedora-Cloud-Base-Generic-45-20261022.0.riscv64.qcow2Fedora-Cloud-Base-Generic-45-20261022.0.riscv64.qcow2.sha256fedora.ini:161-166
fedora-cloud-45.s390xs390xplatformsecondaryFedora-Cloud-Base-Generic-45-1.4.s390x.qcow2Fedora-Cloud-45-1.4-s390x-CHECKSUMfedora.ini:168-172

URL patterns

TreeReleasesURL directory
current43 to 45, x86_64 and aarch64https://download.fedoraproject.org/pub/fedora/linux/releases/R/Cloud/ARCH/images/
archive38 to 42, x86_64 and aarch64https://dl.fedoraproject.org/pub/archive/fedora/linux/releases/R/Cloud/ARCH/images/
alt/risc-v42 to 45, riscv64https://dl.fedoraproject.org/pub/alt/risc-v/release/R/Cloud/riscv64/images/
archive, secondary42, s390xhttps://dl.fedoraproject.org/pub/archive/fedora-secondary/releases/42/Cloud/s390x/images/
secondary43 to 45, s390xhttps://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 by download-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

Firmware and machines

  • x86_64: q35, -cpu max, OVMF from the host or the snap (sys-firmware).
  • aarch64: virt, -cpu max; fedora-cloud-38 uses Fedora's EDK2 from GARDEN_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

ARCHITECTURES · machines and firmware

RUNTIME · make rules and the CLI

FIRST BOOT · cloud-init changes

PKGPROXY · caching for guests