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
- Snap, container or native package — how a package compares with the snap and the container
01 From your package manager
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
Virtualizationproject) 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_HOMEfor the cache (README.md:96-106). - Every install runs the same
image-gardenscript on the sameimage-garden.mk(three ways in).
Read more
02 What your distribution fills in
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 installinstalls, theimage-gardenscript andimage-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>fromPATH; a missing one is a warning, for example for x86_64 (mk/010-qemu-x86_64.mk:3-4);qemu-imgis 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/AAVMFand/usr/share/qemu. See firmware. PKGPROXY_URLgives 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_DIRis$XDG_CACHE_HOME/image-garden, andXDG_CACHE_HOMEdefaults to~/.cache(mk/000-garden.mk:9-12).
03 Older than upstream
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.
Read more
04 Three commands tell you what you have
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) printsimage-garden VERSION, the version written in at install time (image-garden:909-911).image-garden news [N]prints, fromNEWS, thenNEWS.snappyandNEWS.dockerwhere 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'smake installinstalls all three.image-garden make list-systemsechoes every name inGARDEN_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 themubuntu-core-24+tpm.x86_64andopencloudos-cloud-9.loongarch64.
Read more
05 A system your version doesn't know
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.runprintedmake: *** 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-systemsnames 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).
Read more
06 Where to go from here
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
| Distribution | Package |
|---|---|
| Arch Linux | AUR: image-garden |
| Debian | packaged on salsa.debian.org |
| Fedora | image-garden in Fedora |
| openSUSE | Virtualization/image-garden on the Open Build Service |
What to check in a packaged image-garden
image-garden versionagainst the newest release: features such as the +tpm systems, loongarch64 and image downloads through pkgproxy need image-garden 0.8.0.image-garden newsprints 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
| Command | Prints |
|---|---|
image-garden version | image-garden VERSION |
image-garden news | the newest "Changes in" section of each installed NEWS file |
image-garden news N | that section and N more |
image-garden make list-systems | every 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
- The support matrix — every system the release on this map knows
RUNTIME · make rules and the CLI
- image-garden make and the other commands — the commands a package gives you
SNAP · snap-only features
- The image-garden snap — the snap, which follows upstream releases
NATIVE · packages
- What a native install needs from the host — the tools and emulators a package expects to find on your system
- Living with the distribution QEMU — what the distribution's QEMU means for pkgproxy
- Installing from source — build the newest release yourself when the package lags