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

▶ Watch this deck — 7 scenes, ~5 min

01 What runs where

WHAT RUNS WHERE almalinux-cloud-9 efi efi — — — — fedora-cloud-42 efi efi efi platform — — opencloudos-cloud-9 efi efi — — — efi ubuntu-cloud-24.04 efi efi efi platform platform — ubuntu-core-24 efi efi — — — — 13 families, 139 systems, and 19 Ubuntu Core names x86_64 aarch64 riscv64 s390x ppc64 loongarch64 efi ubuntu-cloud-24.04.x86_64: one cell the whole grid is under this deck
A grid: rows are systems, from 13 distribution families with 139 systems and 19 Ubuntu Core names; columns are the six architectures x86_64, aarch64, riscv64, s390x, ppc64 and loongarch64. The cell of ubuntu-cloud-24.04 under x86_64, efi, is the running example; the full table is under the deck

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.mk adds 9 x86_64 systems, 6 aarch64 systems and 4 x86_64 +tpm systems to GARDEN_SYSTEMS, 19 in all (mk/050-ubuntu-core.mk:4-16).
  • The architectures are x86_64, aarch64, riscv64, s390x, ppc64 and loongarch64 (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.

02 Reading the grid

READING THE GRID ubuntu-cloud-24.04 archlinux-cloud x86_64 aarch64 ppc64 ubuntu-cloud-24.04.x86_64 efi efi platform efi — — efi: UEFI firmware bios: legacy BIOS platform: s390x, ppc64 $ image-garden make archlinux-cloud.aarch64.run make: *** No rule to make target 'archlinux-cloud.aarch64.run'. Stop. $ image-garden make ubuntu-cloud-24.04.x86_64.run a filled cell: make knows how
Rows ubuntu-cloud-24.04 and archlinux-cloud, columns x86_64, aarch64 and ppc64. Joining the row and the column gives ubuntu-cloud-24.04.x86_64; a cell's word is efi, bios or platform; a dash, as for archlinux-cloud on aarch64, means no such system and make has no rule for it. Every filled cell, such as ubuntu-cloud-24.04.x86_64, is a system make knows how to build

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 Arch value, and its URL the architecture's name (amd64 also counts for x86_64, arm64 for aarch64) (rulegen.py:395-416). Ubuntu's POWER sections end in .ppc64el and still pass, as they contain ppc64: see Ubuntu cloud images.
  • Boot must be one the architecture has rules for: efi or bios on x86_64, efi on aarch64, riscv64 and loongarch64; s390x and ppc64 boot platform and need no Boot (rulegen.py:300-333). A section without a valid Boot stops rulegen.py, so every section in the data has rules.
  • Every section adds its name to GARDEN_SYSTEMS and 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.

03 The widest coverage, Ubuntu and Fedora

THE WIDEST x86_64 aarch64 riscv64 s390x ppc64 loongarch64 ubuntu, 23 releases 23 10 5 8 10 — 10 the only ppc64 systems fedora, 38 to 45 8 8 4 4 — — the other eleven 30 28 — — — 1 every family 61 46 9 12 10 1 9 12 all from Ubuntu and Fedora a mainframe (s390x) or RISC-V: test on Ubuntu and Fedora
Systems per architecture: Ubuntu has 23 on x86_64, 10 on aarch64, 5 on riscv64, 8 on s390x and 10 on ppc64, the only ppc64 systems; Fedora has 8, 8, 4 and 4; the other eleven families have 30 on x86_64, 28 on aarch64 and 1 on loongarch64. Together Ubuntu and Fedora are all 9 riscv64 and all 12 s390x systems

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).

04 The narrowest coverage

THE NARROWEST x86_64 aarch64 riscv64 s390x ppc64 loongarch64 archlinux-cloud efi — — — — — oracle-cloud-7 bios — — — — — ubuntu 16.10 to 24.10, 13 efi — — — — — nine families efi efi — — — — AlmaLinux, Alpine, Amazon Linux, CentOS, Debian, Gentoo, openSUSE, Oracle, Rocky opencloudos-cloud-9 efi efi — — — efi efi the one loongarch64 system an empty cell: no image is defined for it
Arch Linux, Oracle Linux 7 and thirteen end-of-life Ubuntu interim releases are x86_64 only; nine families have x86_64 and aarch64 only; opencloudos-cloud-9 is the one loongarch64 system, next to its x86_64 and aarch64 builds. An empty cell means no image is defined

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_64 is Arch Linux's only section (data/archlinux.ini); oracle-cloud-7 has 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-9 has 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).

05 Boot types follow the architecture

BOOT TYPES x86_64 aarch64 riscv64 loongarch64 s390x ppc64 efi: 111 systems bios: 6 systems Amazon Linux 2, CentOS 9, 10, Oracle 7, 8, 9: all x86_64 platform: 22 systems no firmware file at all you don't choose it: it comes with the system's name
x86_64, aarch64, riscv64 and loongarch64 lead to efi, 111 systems; x86_64 also leads to bios, six systems: Amazon Linux 2, CentOS 9 and 10, Oracle 7, 8 and 9; s390x and ppc64 lead to platform, 22 systems, with no firmware file. The boot type comes with the name

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

  • Boot is one of platform, efi and bios (rulegen.py:17-20), checked against the architecture: s390x and ppc64 accept only platform, the default there when the key is missing; every other architecture needs Boot (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_64 and oracle-cloud-9.x86_64 (data/amazonlinux.ini, data/centos.ini, data/oracle.ini).
  • Counted at the tag: 111 sections with Boot=efi, 6 with Boot=bios, and the 22 s390x and ppc64 sections without Boot.
  • A section that leaves Boot out on x86_64, aarch64, riscv64 or loongarch64, or names one the architecture has no rules for, stops rulegen.py with FILE: error: Image 'SECTION' has no Boot=, use efi or bios for x86_64 or ... 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

LIST-SYSTEMS $ image-garden make list-systems ubuntu-core-16.x86_64 … ubuntu-core-26+dangerous+tpm.x86_64 almalinux-cloud-8.x86_64 … ubuntu-cloud-24.04.x86_64 … ubuntu-cloud-26.10.ppc64el one per line, every architecture ubuntu-cloud-24.04@web.x86_64 with the instances in your .image-garden.mk $ image-garden make Usage: image-garden make <SYSTEM>.{run,qcow2} … To create a disk image and boot script … image-garden make <random>.run your host's architecture only image-garden make all builds them image-garden make fetch downloads them
image-garden make list-systems prints one system per line: the Ubuntu Core systems, your named instances and every cloud system of every architecture. image-garden make with no goal prints a help with one system picked at random. image-garden make all builds and image-garden make fetch downloads every system of the host's architecture

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-systems prints GARDEN_SYSTEMS one 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:: and fetch get a system only when GARDEN_ARCH equals its architecture (rulegen.py:456-458, rulegen.py:480-484). GARDEN_ARCH defaults to GARDEN_HOST_ARCH, which is uname -m with ppc64le named ppc64, so a POWER host builds the ppc64 systems (mk/000-garden.mk:14-18).
  • Ubuntu Core joins all:: and fetch only on x86_64 and aarch64, the architectures it has rules for (mk/050-ubuntu-core.mk:186-197). Named instances join all too (README.md:529-540).

07 Where to go from here

ROADS The support matrix System names how a name is put together Ubuntu cloud images release by release Ubuntu Core images with modifiers Six architectures the QEMU machine per column Boot types efi, bios, platform loongarch64 OpenCloudOS 9 Adding a row for contributors
Roads from the support matrix: system names, Ubuntu cloud images, Ubuntu Core, the six architectures, boot types, loongarch64 and, for contributors, adding a row

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 namex86_64aarch64riscv64s390xppc64loongarch64
almalinux-cloud-8efiefi————
almalinux-cloud-9efiefi————
almalinux-cloud-10efiefi————
alpine-cloud-3efiefi————
amazonlinux-cloud-2biosefi————
amazonlinux-cloud-2023efiefi————
archlinux-cloudefi—————
centos-cloud-9biosefi————
centos-cloud-10biosefi————
debian-cloud-10efiefi————
debian-cloud-11efiefi————
debian-cloud-12efiefi————
debian-cloud-13efiefi————
debian-cloud-14efiefi————
debian-cloud-sidefiefi————
fedora-cloud-38efiefi————
fedora-cloud-39efiefi————
fedora-cloud-40efiefi————
fedora-cloud-41efiefi————
fedora-cloud-42efiefiefiplatform——
fedora-cloud-43efiefiefiplatform——
fedora-cloud-44efiefiefiplatform——
fedora-cloud-45efiefiefiplatform——
gentoo-cloudefiefi————
opencloudos-cloud-9efiefi———efi
opensuse-cloud-15.4efiefi————
opensuse-cloud-15.5efiefi————
opensuse-cloud-15.6efiefi————
opensuse-cloud-16.0efiefi————
opensuse-cloud-16.1efiefi————
opensuse-cloud-tumbleweedefiefi————
oracle-cloud-7bios—————
oracle-cloud-8biosefi————
oracle-cloud-9biosefi————
oracle-cloud-10efiefi————
rocky-cloud-8efiefi————
rocky-cloud-9efiefi————
rocky-cloud-10efiefi————
ubuntu-cloud-14.04efiefi——platform—
ubuntu-cloud-16.04efiefi——platform—
ubuntu-cloud-16.10efi—————
ubuntu-cloud-17.04efi—————
ubuntu-cloud-17.10efi—————
ubuntu-cloud-18.04efiefi—platformplatform—
ubuntu-cloud-18.10efi—————
ubuntu-cloud-19.04efi—————
ubuntu-cloud-19.10efi—————
ubuntu-cloud-20.04efiefi—platformplatform—
ubuntu-cloud-20.10efi—————
ubuntu-cloud-21.04efi—————
ubuntu-cloud-21.10efi—————
ubuntu-cloud-22.04efiefi—platformplatform—
ubuntu-cloud-22.10efi—————
ubuntu-cloud-23.04efi—————
ubuntu-cloud-23.10efi—————
ubuntu-cloud-24.04efiefiefiplatformplatform—
ubuntu-cloud-24.10efi—————
ubuntu-cloud-25.04efiefiefiplatformplatform—
ubuntu-cloud-25.10efiefiefiplatformplatform—
ubuntu-cloud-26.04efiefiefiplatformplatform—
ubuntu-cloud-26.10efiefiefiplatformplatform—

Ubuntu Core

System namex86_64aarch64
ubuntu-core-16, -18, -20efi—
ubuntu-core-22, -24, -26efiefi
ubuntu-core-22+dangerous, -24+dangerous, -26+dangerousefiefi
ubuntu-core-24+tpm, -26+tpmefi, Secure Boot, TPM—
ubuntu-core-24+dangerous+tpm, -26+dangerous+tpmefi, 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.com for 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-24 and ubuntu-core-24+tpm; image-garden downloads it once.
  • Named instances add @NAME before the architecture, such as ubuntu-cloud-24.04@webserver.x86_64: see named instances.

Roads from here

START HERE

SYSTEMS · distributions

UBUNTU CORE · all snaps

ARCHITECTURES · machines and firmware

BUILD TIME · data and rules