The support matrix
distro × release × arch for everyone
139 systems from 13 distribution families, plus 19 Ubuntu Core systems, across x86_64, aarch64, riscv64, s390x, ppc64 and loongarch64, each cell with its boot type; Ubuntu and Fedora reach the most architectures, Arch Linux only x86_64, OpenCloudOS alone loongarch64.
On the map: systems
01 What runs where
13 distribution families with 139 systems, plus 19 Ubuntu Core systems, across six architectures. The full table is under this deck.
Say you need to know whether image-garden can run the system you care about, on the architecture you need. The answer is a grid. Down the side are the systems: thirteen distribution families, from AlmaLinux to Ubuntu, 139 systems in all, plus nineteen Ubuntu Core names. Across the top are six architectures: x86_64, aarch64, riscv64, s390x, ppc64 and loongarch64. Our running example, ubuntu-cloud-24.04.x86_64, is one cell. The whole grid is under this deck. These scenes show how to read it, where it's thick, where it's thin, and how to list it yourself.
Details and sources
Details
- The data directory has 13 INI files, one per family: almalinux, alpine, amazonlinux, archlinux, centos, debian, fedora, gentoo, opencloudos, opensuse, oracle, rocky and ubuntu, with 139 system sections between them (counted at the tag).
- Ubuntu Core is not in the INI files:
mk/050-ubuntu-core.mkadds 9 x86_64 systems, 6 aarch64 systems and 4 x86_64+tpmsystems toGARDEN_SYSTEMS, 19 in all (mk/050-ubuntu-core.mk:4-16). - The architectures are
x86_64,aarch64,riscv64,s390x,ppc64andloongarch64(rulegen.py:23-29); the README lists the same and the families per architecture (README.md:589-606). - The running example's section is ubuntu.ini:237-242.
Read more
02 Reading the grid
Row plus column is the system name: ubuntu-cloud-24.04 + x86_64. A cell gives the boot type; a dash means no such system, so no rule.
Each row is a system name without its architecture, such as ubuntu-cloud-24.04. Each column is an architecture. Join the two with a dot and you have the name make understands: ubuntu-cloud-24.04.x86_64. The word in a cell says how that system boots: efi, bios or platform. A dash means there's no such system, so there's no rule to build it, and make will say it doesn't know how. Every filled cell is a system make knows how to build. The grid comes from the same data as the build, so it's exactly what the build turned into rules.
Details and sources
Details
- A section name must contain its
Archvalue, and its URL the architecture's name (amd64also counts for x86_64,arm64for aarch64) (rulegen.py:395-416). Ubuntu's POWER sections end in.ppc64eland still pass, as they containppc64: see Ubuntu cloud images. Bootmust be one the architecture has rules for:efiorbioson x86_64,efion aarch64, riscv64 and loongarch64; s390x and ppc64 bootplatformand need noBoot(rulegen.py:300-333). A section without a validBootstops rulegen.py, so every section in the data has rules.- Every section adds its name to
GARDEN_SYSTEMSand gets its rules (rulegen.py:453-478). A name with no section has no rule; the message is GNU make's own "No rule to make target" (derived). - Instances, such as
ubuntu-cloud-24.04@web.x86_64, are rows your project adds: see named instances.
Read more
03 The widest coverage, Ubuntu and Fedora
Ubuntu covers five architectures and is the only family on ppc64; Fedora covers four. Together they are all 9 riscv64 and all 12 s390x systems.
Two families cover the most ground. Ubuntu reaches five architectures: every release on x86_64, its long-term and newest releases on aarch64 and ppc64, most of them on s390x, and riscv64 from 24.04 on. It's the only family on ppc64 at all. Fedora reaches four: every release from 38 to 45 on x86_64 and aarch64, and from 42 on riscv64 and s390x too. Between them, Ubuntu and Fedora are every riscv64 and every s390x system there is. So if your tool has to work on a mainframe or on RISC-V, these are the systems you'll test it on.
Details and sources
Details
- Ubuntu: 23 releases on x86_64; aarch64 and ppc64 for 14.04, 16.04, 18.04, 20.04, 22.04, 24.04, 25.04, 25.10, 26.04 and 26.10; s390x from 18.04 for the same; riscv64 for 24.04, 25.04, 25.10, 26.04 and 26.10 (data/ubuntu.ini, README.md:683-697).
- Fedora: 38 to 45 on x86_64 and aarch64, 42 to 45 on riscv64 and s390x (data/fedora.ini, README.md:643-649).
- Systems per architecture, all families: x86_64 61, aarch64 46, s390x 12, ppc64 10, riscv64 9, loongarch64 1 (counted at the tag).
Read more
04 The narrowest coverage
Arch Linux, Oracle Linux 7 and the end-of-life Ubuntu interim releases are x86_64 only. Nine families have x86_64 and aarch64. opencloudos-cloud-9 is the one loongarch64 system.
At the other end, Arch Linux is x86_64 only: one rolling image, one cell. Oracle Linux 7 and thirteen Ubuntu interim releases past their end of life are x86_64 only too. Most families sit in the middle, on x86_64 and aarch64 and nothing else: AlmaLinux, Alpine, Amazon Linux, CentOS, Debian, Gentoo, openSUSE, Oracle and Rocky. And loongarch64 has a column almost to itself. OpenCloudOS 9 is its one system, next to OpenCloudOS's x86_64 and aarch64 builds. An empty cell isn't a setting you can turn on: no image is defined for it.
Details and sources
Details
archlinux-cloud.x86_64is Arch Linux's only section (data/archlinux.ini);oracle-cloud-7has no aarch64 section (data/oracle.ini).- Ubuntu 16.10, 17.04, 17.10, 18.10, 19.04, 19.10, 20.10, 21.04, 21.10, 22.10, 23.04, 23.10 and 24.10 have only an x86_64 section (data/ubuntu.ini).
- AlmaLinux, Alpine, Amazon Linux, CentOS, Debian, Gentoo, openSUSE, Oracle and Rocky have x86_64 and aarch64 sections only.
opencloudos-cloud-9has x86_64, aarch64 and loongarch64 sections (data/opencloudos.ini); the README calls it the only loongarch64 system (README.md:605-606).- OpenCloudOS publishes each build in a directory of its own, on the project's own mirror, so the section pins a build (data/opencloudos.ini:4-7).
Read more
05 Boot types follow the architecture
111 systems boot efi, 6 x86_64 systems bios, and the 22 s390x and ppc64 systems platform, with no firmware file.
The word in a cell is the boot type, and the architecture mostly decides it. On x86_64, aarch64, riscv64 and loongarch64, systems boot through UEFI firmware: 111 systems boot efi. Six x86_64 systems need a legacy BIOS instead: Amazon Linux 2, CentOS 9 and 10, and Oracle 7, 8 and 9. On s390x and ppc64 there's no firmware to choose. The 22 systems there boot the platform's own way, with no firmware file at all. You don't pick the boot type yourself; it comes with the name.
Details and sources
Details
Bootis one ofplatform,efiandbios(rulegen.py:17-20), checked against the architecture: s390x and ppc64 accept onlyplatform, the default there when the key is missing; every other architecture needsBoot(rulegen.py:300-333).- rulegen.py picks the image rules by architecture and boot type: x86_64 efi or bios, aarch64, riscv64 and loongarch64 efi, s390x and ppc64 whatever the boot type (rulegen.py:804-821).
- The bios systems:
amazonlinux-cloud-2.x86_64,centos-cloud-9.x86_64,centos-cloud-10.x86_64,oracle-cloud-7.x86_64,oracle-cloud-8.x86_64andoracle-cloud-9.x86_64(data/amazonlinux.ini, data/centos.ini, data/oracle.ini). - Counted at the tag: 111 sections with
Boot=efi, 6 withBoot=bios, and the 22 s390x and ppc64 sections withoutBoot. - A section that leaves
Bootout on x86_64, aarch64, riscv64 or loongarch64, or names one the architecture has no rules for, stops rulegen.py withFILE: error: Image 'SECTION' has no Boot=, use efi or bios for x86_64or... has Boot=bios, which aarch64 does not support, use efi(rulegen.py:312-333, rulegen.py:753-757).
Read more
06 Listing the systems yourself
image-garden make list-systems prints every system, instances included. all builds and fetch downloads every system of the host's architecture.
To see every name at once, ask make: image-garden make list-systems. It prints one system per line, every architecture included, with the Ubuntu Core names and any named instances your project defines in .image-garden.mk. That's the list to search for what you need. Typing image-garden make with no goal prints a short help, with one system picked at random as an example. Two more targets work on your host's own architecture only: image-garden make all builds every such system, and image-garden make fetch only downloads them, for later work offline.
Details and sources
Details
list-systemsprintsGARDEN_SYSTEMSone per line, in the order the makefile adds them: Ubuntu Core first (mk/050-ubuntu-core.mk), then the instances of your project's.image-garden.mk, then the INI families in file order (mk/000-garden.mk:69-87, Makefile:48-50).- The default goal is
help, which prints the usage and an example with a random system (mk/000-garden.mk:71-83). all::andfetchget a system only whenGARDEN_ARCHequals its architecture (rulegen.py:456-458, rulegen.py:480-484).GARDEN_ARCHdefaults toGARDEN_HOST_ARCH, which isuname -mwithppc64lenamedppc64, so a POWER host builds the ppc64 systems (mk/000-garden.mk:14-18).- Ubuntu Core joins
all::andfetchonly on x86_64 and aarch64, the architectures it has rules for (mk/050-ubuntu-core.mk:186-197). Named instances joinalltoo (README.md:529-540).
Read more
07 Where to go from here
Next: system names, Ubuntu and Ubuntu Core, the six architectures, boot types, loongarch64, and, for contributors, adding a row.
So the grid is every system image-garden has, cell for cell. From here, the naming deck shows how a system name is put together. The Ubuntu deck walks the widest row family, release by release, and the Ubuntu Core deck covers the images with modifiers. The architecture deck shows the QEMU machine behind each column, and the boot deck what efi, bios and platform change. loongarch64 has a deck of its own, and a deck for contributors shows how to add a row.
Details and sources
Read more
Basis of the statements on this page
The tables are generated from the data/*.ini files of image-garden v0.8.0 ("code"): every section is one system. Ubuntu Core comes from mk/050-ubuntu-core.mk and the README. Each cell gives the boot type: efi (UEFI firmware), bios, or platform (the architecture's own boot, on s390x and ppc64).
How to read a system name
A row's system is NAME.ARCH, for example ubuntu-cloud-24.04.x86_64 or fedora-cloud-42.riscv64. image-garden make NAME.ARCH.run builds and boots it; image-garden make list-systems lists every name. See system names.
Cloud images: 139 systems in 13 families
| System name | x86_64 | aarch64 | riscv64 | s390x | ppc64 | loongarch64 |
|---|---|---|---|---|---|---|
almalinux-cloud-8 | efi | efi | — | — | — | — |
almalinux-cloud-9 | efi | efi | — | — | — | — |
almalinux-cloud-10 | efi | efi | — | — | — | — |
alpine-cloud-3 | efi | efi | — | — | — | — |
amazonlinux-cloud-2 | bios | efi | — | — | — | — |
amazonlinux-cloud-2023 | efi | efi | — | — | — | — |
archlinux-cloud | efi | — | — | — | — | — |
centos-cloud-9 | bios | efi | — | — | — | — |
centos-cloud-10 | bios | efi | — | — | — | — |
debian-cloud-10 | efi | efi | — | — | — | — |
debian-cloud-11 | efi | efi | — | — | — | — |
debian-cloud-12 | efi | efi | — | — | — | — |
debian-cloud-13 | efi | efi | — | — | — | — |
debian-cloud-14 | efi | efi | — | — | — | — |
debian-cloud-sid | efi | efi | — | — | — | — |
fedora-cloud-38 | efi | efi | — | — | — | — |
fedora-cloud-39 | efi | efi | — | — | — | — |
fedora-cloud-40 | efi | efi | — | — | — | — |
fedora-cloud-41 | efi | efi | — | — | — | — |
fedora-cloud-42 | efi | efi | efi | platform | — | — |
fedora-cloud-43 | efi | efi | efi | platform | — | — |
fedora-cloud-44 | efi | efi | efi | platform | — | — |
fedora-cloud-45 | efi | efi | efi | platform | — | — |
gentoo-cloud | efi | efi | — | — | — | — |
opencloudos-cloud-9 | efi | efi | — | — | — | efi |
opensuse-cloud-15.4 | efi | efi | — | — | — | — |
opensuse-cloud-15.5 | efi | efi | — | — | — | — |
opensuse-cloud-15.6 | efi | efi | — | — | — | — |
opensuse-cloud-16.0 | efi | efi | — | — | — | — |
opensuse-cloud-16.1 | efi | efi | — | — | — | — |
opensuse-cloud-tumbleweed | efi | efi | — | — | — | — |
oracle-cloud-7 | bios | — | — | — | — | — |
oracle-cloud-8 | bios | efi | — | — | — | — |
oracle-cloud-9 | bios | efi | — | — | — | — |
oracle-cloud-10 | efi | efi | — | — | — | — |
rocky-cloud-8 | efi | efi | — | — | — | — |
rocky-cloud-9 | efi | efi | — | — | — | — |
rocky-cloud-10 | efi | efi | — | — | — | — |
ubuntu-cloud-14.04 | efi | efi | — | — | platform | — |
ubuntu-cloud-16.04 | efi | efi | — | — | platform | — |
ubuntu-cloud-16.10 | efi | — | — | — | — | — |
ubuntu-cloud-17.04 | efi | — | — | — | — | — |
ubuntu-cloud-17.10 | efi | — | — | — | — | — |
ubuntu-cloud-18.04 | efi | efi | — | platform | platform | — |
ubuntu-cloud-18.10 | efi | — | — | — | — | — |
ubuntu-cloud-19.04 | efi | — | — | — | — | — |
ubuntu-cloud-19.10 | efi | — | — | — | — | — |
ubuntu-cloud-20.04 | efi | efi | — | platform | platform | — |
ubuntu-cloud-20.10 | efi | — | — | — | — | — |
ubuntu-cloud-21.04 | efi | — | — | — | — | — |
ubuntu-cloud-21.10 | efi | — | — | — | — | — |
ubuntu-cloud-22.04 | efi | efi | — | platform | platform | — |
ubuntu-cloud-22.10 | efi | — | — | — | — | — |
ubuntu-cloud-23.04 | efi | — | — | — | — | — |
ubuntu-cloud-23.10 | efi | — | — | — | — | — |
ubuntu-cloud-24.04 | efi | efi | efi | platform | platform | — |
ubuntu-cloud-24.10 | efi | — | — | — | — | — |
ubuntu-cloud-25.04 | efi | efi | efi | platform | platform | — |
ubuntu-cloud-25.10 | efi | efi | efi | platform | platform | — |
ubuntu-cloud-26.04 | efi | efi | efi | platform | platform | — |
ubuntu-cloud-26.10 | efi | efi | efi | platform | platform | — |
Ubuntu Core
| System name | x86_64 | aarch64 |
|---|---|---|
ubuntu-core-16, -18, -20 | efi | — |
ubuntu-core-22, -24, -26 | efi | efi |
ubuntu-core-22+dangerous, -24+dangerous, -26+dangerous | efi | efi |
ubuntu-core-24+tpm, -26+tpm | efi, Secure Boot, TPM | — |
ubuntu-core-24+dangerous+tpm, -26+dangerous+tpm | efi, Secure Boot, TPM | — |
Modifiers go in alphabetical order (+dangerous+tpm). Ubuntu Core has no root password login: use ubuntu/ubuntu. See Ubuntu Core and Secure Boot and TPM.
Notes
- Ubuntu interim releases that reached their end of life are x86_64 only and use
old-releases.ubuntu.comfor apt; 25.04 and 25.10 are not there yet. - Arch Linux and Gentoo are rolling: their names carry no release.
- Several systems can share one downloaded image, such as
ubuntu-core-24andubuntu-core-24+tpm; image-garden downloads it once. - Named instances add
@NAMEbefore the architecture, such asubuntu-cloud-24.04@webserver.x86_64: see named instances.
Roads from here
START HERE
- How systems are named — how a system name is put together, with modifiers and instances
SYSTEMS · distributions
- Ubuntu cloud images — the Ubuntu row family, release by release
- Debian cloud images — Debian
- Fedora cloud images — Fedora
- AlmaLinux, CentOS Stream, Oracle Linux and Rocky Linux — AlmaLinux, CentOS, Oracle and Rocky
- openSUSE Leap and Tumbleweed — openSUSE
- Amazon Linux 2 and 2023 — Amazon Linux
- Alpine Linux — Alpine
- Arch Linux — Arch Linux
- Gentoo — Gentoo
- OpenCloudOS — OpenCloudOS
UBUNTU CORE · all snaps
- Ubuntu Core images — the Ubuntu Core rows and their +dangerous and +tpm modifiers
ARCHITECTURES · machines and firmware
- Six architectures, six QEMU machines — the QEMU machine, CPU and acceleration behind each column
- Boot types — what efi, bios and platform change in the rules
- loongarch64 and OpenCloudOS — the one loongarch64 system and what it needs
BUILD TIME · data and rules
- The .ini files in data/ — for contributors, how to add a row