Ubuntu cloud images

14.04 to 26.10 for users

image-garden has every Ubuntu release from 14.04 to 26.10 on x86_64, the LTS and newest releases on up to four more architectures, end-of-life interim releases on x86_64 only with apt pointed at old-releases.ubuntu.com, and POWER systems named .ppc64el.

On the map: systems

▶ Watch this deck — 6 scenes, ~4 min

Worth seeing first

01 Every Ubuntu since 14.04

UBUNTU CLOUD IMAGES the old LTS your users still run, the interim release just out 14.04 16.04 16.10 17.04 17.10 18.04 18.10 19.04 19.10 20.04 20.10 21.04 21.10 22.04 22.10 23.04 23.10 24.04 24.10 25.04 25.10 26.04 26.10 23 releases, Canonical's own cloud images $ image-garden make list-systems \ | grep -c '^ubuntu-cloud-' 56 23 releases, 56 systems 24.04 ubuntu-cloud-24.04.x86_64 which architectures after the end of life the ppc64el names
Twenty-three Ubuntu releases from 14.04 to 26.10, 56 systems, as image-garden make list-systems counts them; ubuntu-cloud-24.04.x86_64 is one of them. The deck covers architectures, end of life and the ppc64el names

56 systems: 23 releases from 14.04 to 26.10, from cloud-images.ubuntu.com.

If your tool runs on Ubuntu, you probably care about more than the newest release: the old LTS your users still have, the interim one that's just out. image-garden keeps the widest Ubuntu shelf of any distribution: every release from 14.04 to 26.10, twenty-three of them, as Canonical's own cloud images. Across their architectures that's fifty-six systems, and our running example, ubuntu-cloud-24.04.x86_64, is one of them. This deck shows which releases reach which architectures, what happens when a release reaches its end of life, and a naming quirk on POWER.

Details and sources

Details

  • data/ubuntu.ini starts with [META]: Group=ubuntu, Variant=cloud (ubuntu.ini:4-6), then one section per system, 56 in all, grouped under codename comments from trusty to stonking.
  • The running example: ubuntu.ini:237-242.
  • The README's Ubuntu list: LTS 14.04 to 26.04, non-LTS 26.10, end-of-life 25.04 and 25.10 not yet archived, and 16.10 to 24.10 end of life (README.md:683-697).
  • Every release, its architectures and its apt source are in the table under this deck.

02 Long-term and interim releases

LTS AND INTERIM x86_64 aarch64 ppc64 s390x riscv64 LTS 14.04, 16.04 LTS 18.04 to 22.04 LTS 24.04, 26.04 25.04, 25.10, 26.10 interim 16.10 to 24.10 — — — — — — — yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes yes ubuntu-cloud-24.04: five, ubuntu-cloud-23.10: one
Every LTS from 14.04 is on x86_64, aarch64 and ppc64, from 18.04 also on s390x, from 24.04 also on riscv64; 25.04, 25.10 and 26.10 are on all five; the interim releases 16.10 to 24.10 only on x86_64. So ubuntu-cloud-24.04 is on five architectures and ubuntu-cloud-23.10 on one

LTS releases are on x86_64, aarch64 and ppc64, s390x from 18.04, riscv64 from 24.04. 25.04 to 26.10 have all five; interim releases from 16.10 to 24.10 only x86_64.

Ubuntu releases come in two kinds. A long-term support release comes every two years, in April. Interim releases come in between and are supported for months, not years. image-garden follows that. Every LTS from 14.04 is there on x86_64, aarch64 and ppc64, from 18.04 on s390x as well, and from 24.04 on riscv64 too. The newest releases, 25.04 onwards, interim or not, have all five. The older interim releases have just one: x86_64. So ubuntu-cloud-24.04 is on five architectures, and ubuntu-cloud-23.10 on one.

Details and sources

Details

  • aarch64 and ppc64 sections: 14.04, 16.04, 18.04, 20.04, 22.04, 24.04, 25.04, 25.10, 26.04, 26.10. s390x: the same from 18.04. riscv64: 24.04, 25.04, 25.10, 26.04, 26.10. x86_64: all 23 (data/ubuntu.ini).
  • The README says the same, with ppc64 "systems named .ppc64el" (README.md:692-697).
  • LTS every two years in April, interim releases supported for months: Ubuntu's release cycle (derived, not in the source).

03 End of life, fixed in place

END OF LIFE ubuntu-cloud-24.04.x86_64 https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img a live directory: Canonical refreshes the image ubuntu-cloud-16.10.x86_64 https://cloud-images.ubuntu.com/releases/yakkety/release-20170719/ubuntu-16.10-server-cloudimg-amd64.img nothing new appears there: fixed for good 13 end-of-life interim releases, x86_64 only 16.10 17.04 17.10 18.10 19.04 19.10 20.10 21.04 21.10 22.10 23.04 23.10 24.10 their packages moved too: apt would look in the wrong place
ubuntu-cloud-24.04.x86_64 points at noble/current on cloud-images.ubuntu.com, refreshed by Canonical; ubuntu-cloud-16.10.x86_64 points at releases/yakkety/release-20170719, fixed for good. Thirteen end-of-life interim releases, 16.10 to 24.10, are x86_64 only, and their packages are no longer where apt looks

Live releases point at …/CODENAME/current/; end-of-life interim releases at …/releases/CODENAME/release…/. Thirteen of them, 16.10 to 24.10, are x86_64 only.

Look at the URL of a live release, such as our 24.04: noble, then current. Canonical refreshes the image in that directory. When an interim release reaches its end of life, its images stay only under releases, then the codename, then a release directory, such as release-20170719 for 16.10. Nothing new will appear there, so those images are fixed for good. image-garden has thirteen such releases, 16.10 to 24.10, all on x86_64. But the image is only half the story. Its packages have moved too, and the guest's apt would look for them in the wrong place.

Details and sources

Details

  • Live releases use https://cloud-images.ubuntu.com/CODENAME/current/, as ubuntu.ini:237-242. End-of-life interim releases use https://cloud-images.ubuntu.com/releases/CODENAME/release-DATE/ or …/release/, as 16.10 and 17.10 (ubuntu.ini:52-77); 25.04 already uses releases/plucky/release/.
  • The thirteen releases with x86_64 only: 16.10, 17.04, 17.10, 18.10, 19.04, 19.10, 20.10, 21.04, 21.10, 22.10, 23.04, 23.10, 24.10 (mk/050-ubuntu.mk:4-12).
  • That Canonical refreshes images under current/ and moves end-of-life archives to old-releases.ubuntu.com is Ubuntu's practice (derived); the makefile's comment gives the rule it uses: a codename missing from archive.ubuntu.com/ubuntu/dists/ needs old-releases (mk/050-ubuntu.mk:4-8).

04 Pointing apt at old-releases

OLD-RELEASES image-garden's list: 16.10 17.04 17.10 … 23.04 23.10 24.10 apt: preserve_sources_list: false primary: - arches: [default] security: - arches: [default] added to the user-data of those releases only uri: http://old-releases.ubuntu.com/ubuntu uri: http://old-releases.ubuntu.com/ubuntu apt update, installs: working 25.04 25.10 end of life, still in the main archive: not on the list yet they join once Ubuntu moves them
image-garden's list of old releases has 16.10 to 24.10; for those, the user-data gets an apt block whose primary and security archives are http://old-releases.ubuntu.com/ubuntu, so apt update and package installs work. 25.04 and 25.10 are end of life but still in the main archive, so not on the list yet

For 16.10 to 24.10 the user-data sets apt's primary and security archives to http://old-releases.ubuntu.com/ubuntu. 25.04 and 25.10 are not on the list yet.

So those thirteen releases get one more block of user-data. image-garden keeps a list of them, and for each one it adds an apt section that rewrites the sources: the main archive and the security archive both become old-releases.ubuntu.com. apt update works again, and so do the package installs in your tests. 25.04 and 25.10 have reached their end of life too, but their packages were still in the main archive when this list was written, so they aren't on it. They'll join once Ubuntu moves them; until then they work like any supported release.

Details and sources

Details

  • UBUNTU_OLD_RELEASES_VERSIONS = 16.10 17.04 17.10 18.10 19.04 19.10 20.10 21.04 21.10 22.10 23.04 23.10 24.10; for group ubuntu and a release in that list, UBUNTU_OLD_RELEASES_APT_CONFIG gives an apt: block with preserve_sources_list: false and primary and security set to http://old-releases.ubuntu.com/ubuntu (mk/050-ubuntu.mk:12-24); EXTRA_CLOUD_INIT_APT_CONFIG calls it (mk/050-ubuntu.mk:26-28).
  • The common template places $(call EXTRA_CLOUD_INIT_APT_CONFIG,$1,$3) near its top, with the group and the release (mk/010-qemu.mk:198); rulegen passes the release as the third argument (rulegen.py:467).
  • 25.04 (plucky) and 25.10 (questing) are end of life but were still in archive.ubuntu.com and not in old-releases when the list was last checked, so they are left out until Ubuntu moves them (mk/050-ubuntu.mk:9-11).
  • After the user-data's own rewrite of https to http in /etc/apt/*.list, a pkgproxy's apt setup still applies to these sources (see per-distro quirks).

05 ppc64el in the name

PPC64EL ppc64 image-garden's and QEMU's ppc64el Ubuntu's, in the system name system ubuntu-cloud-24.04.ppc64el image noble-server-cloudimg-ppc64el.img emulator qemu-system-ppc64 $ image-garden make \ ubuntu-cloud-24.04.ppc64el.run ppc64le uname -m on a POWER host image-garden reads it as ppc64: make all builds these, with 4 CPUs your SYSTEM.$(uname -m): matches no system no firmware file: the pseries machine boots it its own way
Three spellings of 64-bit POWER: image-garden's and QEMU's ppc64, Ubuntu's ppc64el in the system name ubuntu-cloud-24.04.ppc64el, on qemu-system-ppc64, which is what make and allocate take, and uname -m's ppc64le on a POWER host, which image-garden reads as ppc64, so make all builds these systems there with 4 CPUs; a script that appends uname -m still matches no system. No firmware file: the pseries machine boots them its own way

Ubuntu's POWER systems are named ubuntu-cloud-R.ppc64el and run on qemu-system-ppc64, with no firmware file. image-garden counts a ppc64le host as ppc64; $(uname -m) in your own scripts matches nothing.

One naming quirk. image-garden calls 64-bit POWER ppc64, as QEMU does, but Ubuntu's images are little-endian, which Ubuntu calls ppc64el, and that's what these systems are named: ubuntu-cloud-24.04.ppc64el, running on QEMU's ppc64 emulator. That name is what you give make and allocate. On a POWER host, uname -m prints ppc64le, a third spelling. image-garden reads it as ppc64, so make all builds these systems there, with four CPUs each. A script of yours that appends uname -m still matches no system. And they need no firmware file: the pseries machine boots them its own way.

Details and sources

Details

  • Ubuntu's POWER sections are named ubuntu-cloud-R.ppc64el, with Arch=ppc64 and no Boot (ubuntu.ini:24-28, ubuntu.ini:264-268). rulegen requires only that the name contain the Arch value, which ppc64el does (rulegen.py:395-405).
  • A missing Boot means platform, the only boot type ppc64 accepts (rulegen.py:300-333); ppc64 systems get the ppc64 rules, with the pseries machine (rulegen.py:820-821, mk/010-qemu-ppc64.mk:4-5).
  • uname -m prints ppc64le on a little-endian POWER host (derived). The README's spread example appends $(uname -m) to the system name (README.md:740-745), which gives no Ubuntu POWER system there.
  • GARDEN_HOST_ARCH is uname -m with ppc64le named ppc64, and GARDEN_ARCH defaults to it (mk/000-garden.mk:14-17). The rules compare GARDEN_ARCH with ppc64 (rulegen.py:456-458), so image-garden make all on a POWER host builds the ppc64el systems, and QEMU_SMP_PPC64 is the variable raised to 4 (mk/010-qemu.mk:5-6). NEWS: "On a ppc64le host the ppc64 systems are native" (NEWS:19-20).
  • Named instances of these systems take their QEMU architecture from the base's Arch=, not from the .ppc64el suffix, so their .run scripts have the ppc64 command and they join all on a POWER host (mk/020-instances.mk:53-65).

06 Where to go from here

ROADS Ubuntu cloud images System names how a name is put together Ubuntu Core the all-snaps images The support matrix every family side by side Six architectures the ppc64 and s390x machines Per-distro quirks changes by distribution ppc64 POWER in full
Roads from Ubuntu cloud images: system names, Ubuntu Core, the support matrix, six architectures, per-distro quirks and ppc64

Next: system names, Ubuntu Core, the support matrix, the six architectures, per-distro quirks and ppc64.

So Ubuntu is twenty-three releases, five architectures, and an apt rewrite for the ones that are gone. From here, the naming deck shows how these system names are put together, and the Ubuntu Core deck covers the all-snaps images. The support matrix sets Ubuntu beside every other family, and the architecture deck shows the machines behind ppc64 and s390x. The quirks deck lists the other per-distribution changes, and the ppc64 deck takes POWER and its ppc64el systems in full.

Details and sources

Read more

Basis of the statements on this page

The table is generated from data/ubuntu.ini and mk/050-ubuntu.mk of image-garden at the tag in garden.commit ("code"): the codenames are the file's comments, the architecture suffixes its section names. Which releases are LTS and which have reached their end of life is Ubuntu's release cycle ("derived"), as the makefile's comments record it. Nothing was run for this page.

Every Ubuntu release

The system name is ubuntu-cloud-RELEASE.SUFFIX, such as ubuntu-cloud-24.04.x86_64 or ubuntu-cloud-24.04.ppc64el. The apt column is where the first boot points apt; image-garden changes it only for the releases marked old-releases.

ReleaseCodenameKindSuffixesapt archive
14.04trustyLTSx86_64, aarch64, ppc64elarchive.ubuntu.com
16.04xenialLTSx86_64, aarch64, ppc64elarchive.ubuntu.com
16.10yakketyinterim, end of lifex86_64old-releases.ubuntu.com
17.04zestyinterim, end of lifex86_64old-releases.ubuntu.com
17.10artfulinterim, end of lifex86_64old-releases.ubuntu.com
18.04bionicLTSx86_64, aarch64, s390x, ppc64elarchive.ubuntu.com
18.10cosmicinterim, end of lifex86_64old-releases.ubuntu.com
19.04discointerim, end of lifex86_64old-releases.ubuntu.com
19.10eoaninterim, end of lifex86_64old-releases.ubuntu.com
20.04focalLTSx86_64, aarch64, s390x, ppc64elarchive.ubuntu.com
20.10groovyinterim, end of lifex86_64old-releases.ubuntu.com
21.04hirsuteinterim, end of lifex86_64old-releases.ubuntu.com
21.10impishinterim, end of lifex86_64old-releases.ubuntu.com
22.04jammyLTSx86_64, aarch64, s390x, ppc64elarchive.ubuntu.com
22.10kineticinterim, end of lifex86_64old-releases.ubuntu.com
23.04lunarinterim, end of lifex86_64old-releases.ubuntu.com
23.10manticinterim, end of lifex86_64old-releases.ubuntu.com
24.04nobleLTSx86_64, aarch64, riscv64, s390x, ppc64elarchive.ubuntu.com
24.10oracularinterim, end of lifex86_64old-releases.ubuntu.com
25.04pluckyinterim, end of lifex86_64, aarch64, riscv64, s390x, ppc64elarchive.ubuntu.com
25.10questinginterim, end of lifex86_64, aarch64, riscv64, s390x, ppc64elarchive.ubuntu.com
26.04resoluteLTSx86_64, aarch64, riscv64, s390x, ppc64elarchive.ubuntu.com
26.10stonkinginterimx86_64, aarch64, riscv64, s390x, ppc64elarchive.ubuntu.com

How the pieces fit

  • Image URLs: live releases from https://cloud-images.ubuntu.com/CODENAME/current/, end-of-life interim releases from …/releases/CODENAME/release…/, each with its SHA256SUMS (data/ubuntu.ini).
  • Boot: efi on x86_64, aarch64 and riscv64; no Boot key, so platform, on s390x and ppc64.
  • POWER hosts: uname -m prints ppc64le, which image-garden counts as ppc64, so image-garden make all there builds the .ppc64el systems with 4 vCPUs (mk/000-garden.mk:14-17). Named instances of them work too.
  • apt: UBUNTU_OLD_RELEASES_VERSIONS lists the releases whose user-data points apt at http://old-releases.ubuntu.com/ubuntu (mk/050-ubuntu.mk:12-28).
  • Users: root/root and ubuntu/ubuntu, as for every cloud system (insecure on purpose).

Roads from here

START HERE

SYSTEMS · distributions

UBUNTU CORE · all snaps

ARCHITECTURES · machines and firmware

FIRST BOOT · cloud-init changes