Distribution packages

Arch, Debian, Fedora, openSUSE for users

image-garden is packaged for Arch Linux (AUR), Debian, Fedora and openSUSE; a package brings the script and its make rules and uses the distribution's QEMU, firmware and swtpm, and may be older than the upstream release, which image-garden version, news and list-systems reveal.

On the map: native

▶ Watch this deck — 6 scenes, ~4 min

Worth seeing first

01 From your package manager

A PACKAGE Arch Linux (AUR) Debian Fedora openSUSE image-garden image-garden.mk the same as in the snap and the container from your system QEMU, qemu-img EDK2 firmware swtpm, OVMF spread updated with the rest, at your distribution's pace what it relies on how old it is what an older one can't do
Packages from Arch Linux (AUR), Debian, Fedora and openSUSE carry the same image-garden command and image-garden.mk as the snap and the container; QEMU, qemu-img, EDK2 firmware, swtpm, OVMF and spread come from your system. The package is updated with the rest, at your distribution's pace. The deck covers what it relies on, how old it is, and what an older one cannot do.

Arch Linux (AUR), Debian, Fedora and openSUSE package image-garden. The command and the make rules are the same; the tools around them come from your system.

Say you'd rather install image-garden like everything else on your machine, with your distribution's package manager, and have it updated with the rest. Four distributions package it: Arch Linux, in the AUR, Debian, Fedora, and openSUSE, in its Virtualization project. A package gives you the same image-garden command and the same make rules as the snap and the container. What it doesn't bring, it takes from your system. And it moves at your distribution's pace, which matters more than you'd think. This deck is for you if you went this way: what a package relies on, how to tell how old it is, and what an older one can't do.

Details and sources

Details

  • The README links packages for Arch Linux (AUR), Debian (on salsa.debian.org), openSUSE (the Open Build Service's Virtualization project) and Fedora (README.md:96-112).
  • Its comparison table gives packages the system's QEMU, EFI firmware and swtpm, spread as a system package, pkgproxy "With PKGPROXY_URL", virtiofsd as a system package and $XDG_CACHE_HOME for the cache (README.md:96-106).
  • Every install runs the same image-garden script on the same image-garden.mk (three ways in).

02 What your distribution fills in

THE SPLIT the package image-garden image-garden.mk your distribution qemu-system-* you installed, qemu-img EDK2: /usr/share/OVMF, /usr/share/AAVMF, ... swtpm and ovmf, for the +tpm systems spread, a package of its own PKGPROXY_URL=http://HOST:PORT pkgproxy is not bundled ~/.cache/image-garden or $XDG_CACHE_HOME/image-garden
The package brings image-garden and image-garden.mk. Your distribution brings the qemu-system emulators you installed and qemu-img, EDK2 firmware from its usual paths, swtpm and ovmf for the +tpm systems, and spread as its own package. pkgproxy is named with PKGPROXY_URL, and downloads go to ~/.cache/image-garden, or $XDG_CACHE_HOME/image-garden.

The package: image-garden and image-garden.mk. Your system: QEMU, qemu-img, EDK2, swtpm and OVMF, spread. pkgproxy by PKGPROXY_URL; downloads in ~/.cache/image-garden.

Here's the split. The package brings the image-garden script and image-garden.mk, with the rules for every system. Everything that runs comes from your distribution. QEMU and qemu-img, so the architectures you can boot are the emulators you've installed. The EDK2 firmware, found in the places distributions put it. swtpm and ovmf, for the TPM systems. And spread, if you want it, is a package of its own. pkgproxy isn't bundled; you name one with PKGPROXY_URL. Downloads go to ~/.cache/image-garden, unless XDG_CACHE_HOME says otherwise.

Details and sources

Details

  • Derived: a package carries what the tree's make install installs, the image-garden script and image-garden.mk, with the README, NEWS files and man page (Makefile:29-46); the packages themselves were not inspected for this map.
  • The emulator is qemu-system-<arch> from PATH; a missing one is a warning, for example for x86_64 (mk/010-qemu-x86_64.mk:3-4); qemu-img is required (mk/010-qemu.mk:3).
  • The x86_64 firmware list starts with Debian's and Ubuntu's /usr/share/OVMF/…, then Arch Linux's and openSUSE's paths (mk/010-qemu-x86_64.mk:260-270); aarch64 looks in /usr/share/AAVMF and /usr/share/qemu. See firmware.
  • PKGPROXY_URL gives guests a pkgproxy by address, and image downloads go through it too (mk/010-qemu.mk:24-29); a distribution QEMU has no guestfwd patch, so there is no socket mode (the distribution's QEMU).
  • Outside the snap, GARDEN_CACHE_DIR is $XDG_CACHE_HOME/image-garden, and XDG_CACHE_HOME defaults to ~/.cache (mk/000-garden.mk:9-12).

03 Older than upstream

TWO SCHEDULES upstream releases this map your distribution distribution packages may be older than the upstream release: the maintainer's statement a stable release keeps the version it shipped with the +tpm systems a loongarch64 guest images through pkgproxy a feature from a deck missing? check the version first
Upstream releases come one after another, up to the release this map describes, which brought the +tpm systems, a loongarch64 guest and image downloads through pkgproxy. A distribution packages one release and a stable distribution keeps it. The maintainer's statement: distribution packages, such as Debian's and Fedora's, may be older than the upstream release. If a feature is missing, check the version first.

Distribution packages, such as Debian's and Fedora's, may be older than the upstream release: the maintainer's statement. Features on this map may be newer than your package.

A package follows its distribution's schedule, not image-garden's. The maintainer says so plainly: distribution packages, such as Debian's and Fedora's, may be older than the upstream release. A stable release of a distribution usually keeps the version it shipped with. That matters, because image-garden changes with each release. Systems arrive and go, and features come in: the Ubuntu Core systems with a TPM, the first loongarch64 guest, and image downloads through pkgproxy all came with the release this map describes. So when a deck here shows something your install doesn't do, check its version first.

Details and sources

Details

  • Distribution packages, such as Debian's and Fedora's, may be older than the upstream release: the maintainer's statement, not in the source.
  • The Ubuntu Core systems with Secure Boot and a TPM, opencloudos-cloud-9 (the first loongarch64 system) and image downloads through pkgproxy are listed as new features of image-garden 0.8.0, the release this map builds on (NEWS:43-58).
  • Derived: a stable release of a distribution usually updates a package only for fixes, so it keeps the version it shipped with.

04 Three commands tell you what you have

WHAT YOU HAVE $ image-garden version image-garden VERSION $ image-garden news [N] *** Changes in VERSION: *** $ image-garden make list-systems ... ubuntu-cloud-24.04.x86_64 ubuntu-cloud-24.04.aarch64 ... this map's support matrix ubuntu-core-24+tpm.x86_64 not in your list: no TPM systems yet
image-garden version prints the version; image-garden news [N] prints the release notes of that release, or N releases back; image-garden make list-systems prints every system the version knows, such as ubuntu-cloud-24.04.x86_64. Compared with this map's support matrix, a missing ubuntu-core-24+tpm.x86_64 means the package has no TPM systems yet.

image-garden version, image-garden news [N] and image-garden make list-systems. Compare the list with the support matrix.

Three commands tell you what you have. image-garden version prints the version the package was built from. image-garden news prints the notes of that release, and with a number after it, as many releases back, so you can see what came in and when. And image-garden make list-systems prints every system your version knows, one per line, such as ubuntu-cloud-24.04.x86_64. Set that list beside this map's support matrix. A system on the matrix that's missing from your list is newer than your package: no ubuntu-core-24+tpm, for example, means no TPM systems yet.

Details and sources

Details

  • image-garden version (or --version) prints image-garden VERSION, the version written in at install time (image-garden:909-911).
  • image-garden news [N] prints, from NEWS, then NEWS.snappy and NEWS.docker where installed, the newest section, or that and N more, each "Changes in" heading framed with *** (image-garden:912-942). Which NEWS files a package installs is up to the package; the tree's make install installs all three.
  • image-garden make list-systems echoes every name in GARDEN_SYSTEMS, one per line (mk/000-garden.mk:85-87). Run for this map on a source install of v0.8.0: 160 lines, among them ubuntu-core-24+tpm.x86_64 and opencloudos-cloud-9.loongarch64.

05 A system your version doesn't know

NO RULE TO MAKE TARGET $ image-garden make ubuntu-core-26+tpm.x86_64.run make: *** No rule to make target 'ubuntu-core-26+tpm.x86_64.run'. Stop. a typing mistake? a system newer than your package? the same message for both $ image-garden make list-systems not listed: the package predates it the snap container source or wait for your distribution to catch up
image-garden make ubuntu-core-26+tpm.x86_64.run on an older package answers make: *** No rule to make target 'ubuntu-core-26+tpm.x86_64.run'. Stop. The same message comes from a typing mistake, so check image-garden make list-systems; a system that is not listed is newer than the package: wait for the distribution, or use the snap, the container or a source build.

make: *** No rule to make target 'NAME.run'. Stop. means a typo or a system newer than your package. Check list-systems; for newer systems use the snap, the container or a source build.

Here's what an older package says when you ask for a system it doesn't know. image-garden make, with a name from a newer release, gets make's own answer: no rule to make target, the file name, and stop. Nothing about versions. A typing mistake gets exactly the same message, so check the name against list-systems first. If it really isn't there, your package predates it. Then you can wait for your distribution to catch up, or take a way in that follows upstream releases: the snap, the container, or a build from source.

Details and sources

Details

  • Run for this map with a source install, in an empty directory: LC_ALL=C image-garden make no-such-system.x86_64.run printed make: *** No rule to make target 'no-such-system.x86_64.run'. Stop. The message is GNU make's own; image-garden adds nothing to it (image-garden:982-993). With another locale, make prints it in that language.
  • list-systems names what the installed version knows (mk/000-garden.mk:85-87).
  • The snap and the container are built from each release tag (how current each install is); a source build takes any release or commit (installing from source).

06 Where to go from here

ROADS Packages What the host needs tools and emulators The distribution's QEMU pkgproxy by URL A source build the newest release The support matrix every system on this map image-garden make the command line The snap follows upstream releases
Six roads from Distribution packages: what the host needs, the distribution's QEMU, a source build, the support matrix, image-garden make and the snap

Next: what the host needs, the distribution's QEMU, a source build, the support matrix, image-garden make and the snap.

So a package is the easy way in, with your distribution doing the updates, at its own pace. Next, the host tools deck lists what a package expects to find on your system, and the QEMU deck explains why pkgproxy is a URL there. When the package is too old, a source build gets you the newest release in a few minutes. The support matrix shows every system the release on this map knows. And the command line deck, and the snap, are one step away.

Details and sources

Read more

Basis of the statements on this page

The package links are in the README of image-garden at the pinned commit ("code"). That distribution packages, such as Debian's and Fedora's, may be older than the upstream release is the maintainer's statement; check your distribution's version against the release notes before relying on a feature. The command output below was produced by running a source install of v0.8.0; the packages themselves were not inspected.

Where the packages are

DistributionPackage
Arch LinuxAUR: image-garden
Debianpackaged on salsa.debian.org
Fedoraimage-garden in Fedora
openSUSEVirtualization/image-garden on the Open Build Service

What to check in a packaged image-garden

  • image-garden version against the newest release: features such as the +tpm systems, loongarch64 and image downloads through pkgproxy need image-garden 0.8.0.
  • image-garden news prints the release notes of the installed version.
  • The distribution's QEMU lacks the guestfwd unix socket patch: pkgproxy works only through PKGPROXY_URL. See your own QEMU.

The commands that tell you what you have

CommandPrints
image-garden versionimage-garden VERSION
image-garden newsthe newest "Changes in" section of each installed NEWS file
image-garden news Nthat section and N more
image-garden make list-systemsevery system the installed version knows, one per line

When a system is missing

$ image-garden make ubuntu-core-26+tpm.x86_64.run make: *** No rule to make target 'ubuntu-core-26+tpm.x86_64.run'. Stop.

The same message comes from a misspelt name. If list-systems does not list the system, the package is older than the release that added it: wait for the distribution, or use the snap, the container or a source build.

Roads from here

SYSTEMS · distributions

RUNTIME · make rules and the CLI

SNAP · snap-only features

NATIVE · packages