Viewing as everyone topics and scenes not meant for you are faded or hidden

image-garden map

How image-garden turns a few lines of .ini into a running test VM for thirteen distributions and six architectures: the data and rules behind it, what cloud-init changes in each system, the make targets you run, pkgproxy's part, and the snap, container and source builds, one narrated deck per topic. Pick any place, follow the roads at the end of each deck, and switch perspective at the top to see only what applies to you. The caching proxy has its own map: the pkgproxy map.

Source: gitlab.com/zygoon/image-garden-map · report a problem or suggest a change

Journeys

Learning paths through several decks, in order. Pick one to see its route on the map.

START HERE SYSTEMS · distributions UBUNTU CORE · all snaps ARCHITECTURES · machines and firmware RUNTIME · make rules and the CLI SPREAD · tests BUILT ON IT · CI integrations FIRST BOOT · cloud-init changes PKGPROXY · caching for guests SNAP · snap-only features CONTAINER · OCI image NATIVE · packages BUILD TIME · data and rules ON THE SNAPD MAP ↗ From name to a VMthe whole path in one deck⚑ System namesgroup-variant-release.arch⚑ Three ways insnap, container, packages⚑ Insecure on purposefixed passwords, open SSH⚑ What runs wheredistro × release × arch⚑ Ubuntu14.04 to 26.10⚑ Debian10 to 14, sid⚑ Fedora38 to 45, four arches⚑ Enterprise LinuxAlma, CentOS, Oracle, Rocky⚑ Amazon Linux2 and 2023⚑ openSUSELeap 15, 16, Tumbleweed⚑ Alpineone release, small⚑ Arch Linuxrolling, x86_64 only⚑ Gentoorolling, a program URL⚑ OpenCloudOS9, three arches⚑ Ubuntu Core16 to 26, +dangerous⚑ +dangerous systemsyour own kernel or gadget⚑ Secure Boot and TPMubuntu-core-24+tpm, 26+tpm⚑ Six architecturesa QEMU machine for each⚑ efi, bios, platformhow each system boots⚑ EDK2 firmwarecode and vars per system⚑ x86_64q35, OVMF, efi or bios⚑ aarch64virt, EDK2, older firmware⚑ riscv64virt, no ACPI, EDK2⚑ s390xccw, no firmware⚑ ppc64pseries, ppc64el names⚑ loongarch64OpenCloudOS 9⚑ image-garden makethe command line⚑ The target chainfrom .url to .run⚑ Download and verifylock, resume, check, retry⚑ Overlay and first boot64G qcow2, one boot⚑ The .run scriptQEMU_*_OPTION⚑ The serial consolewhy the TTY acts oddly⚑ --querymemory and users⚑ allocatea VM in the background⚑ discard and psstop and list VMs⚑ @instancesmany VMs, one image⚑ swtpm per launchTPM state next to the disk⚑ rebasemoved caches⚑ Where files livecache, project, runtime⚑ Testing with spreada fresh VM for every run⚑ The adhoc backendallocate and discard⚑ Names in spread-plus-, -at-, no arch⚑ Built on itfour components, one action⚑ *craft-gitlab-cisnap, rock and charm builds⚑ Only pkgproxy cachesthe pkgproxy-url input⚑ spread-gitlab-cispread, reports, reruns⚑ The contractwhat they rely on⚑ GitHub actionimage-garden-action⚑ Caching on GitHubpkgproxy, prepared images⚑ GitLab vs GitHubcontainer vs snap⚑ The seed ISOuser-data + meta-data⚑ Picking a templategroup, release, instance⚑ Users and passwordsroot/root, ubuntu/ubuntu⚑ SSH and aptpasswords, root, apt sources⚑ Once, then offpower off, cloud-init off⚑ Per-distro quirksAL2, Gentoo, old Ubuntu⚑ Your own changes.image-garden.mk, EXTRA_*⚑ One base, many VMsprofiles you pay for once⚑ Why pkgproxydownload once⚑ Reaching the host10.0.2.100 or a URL⚑ The guestfwd patchTCP in, unix socket out⚑ In the user-datahosts, apt, snap, GOPROXY⚑ Image downloadsfiles and volatile lists⚑ When it is downseconds, not minutes⚑ No rebuildmode is baked in⚑ The snapstrict, core26⚑ Componentsqemu-*, swtpm, spread⚑ pkgproxy= settingcomponent, none, snap, URL⚑ spread-variantspread or spread-plus⚑ swtpm in the snapa component, an app⚑ virtiofs and 9pshare host files, advanced⚑ Confinement/tmp, RAM and other limits⚑ The containerQEMU, swtpm, firmware⚑ docker run/dev/kvm and a volume⚑ pkgproxy by URLPKGPROXY_URL only⚑ KVM in CIrunners with /dev/kvm⚑ Distro packagesArch, Debian, Fedora, SUSE⚑ make installfrom a source tree⚑ What the host needsQEMU, OVMF, swtpm, curl⚑ Your own QEMUno guestfwd patch⚑ One .ini per distroMETA, sections, keys⚑ Checksums requiredSUMS files or one hash⚑ URLProgramwhen the URL moves⚑ rulegen.py.ini in, make rules out⚑ image-garden.mkthree parts, one file⚑ Hand-written rulesmk/050-*, Ubuntu Core⚑ Model and gradedangerous, signed, secured⚑ Install --dangeroussnap try, pack, install⚑ Kernel command linewhat a gadget allows⚑ Boot modesrun, install, recover⚑ Encryptiongrade decides⚑
point at a topic to read what it covers · ⚑ visited 0 of 0 · dashed: no slides yet · audience: users CI operators contributors

Click a place to enter it. Inside a topic you see only its exits; m brings the whole map back. space plays, ← → step. This map describes image-garden at release v0.8.1 (commit a5785d52). Where it says "the snap" or "the container", it means the ones built from that tree.

All 87 decks as a list (readable without JavaScript)

START HERE

SYSTEMS · distributions

UBUNTU CORE · all snaps

ARCHITECTURES · machines and firmware

RUNTIME · make rules and the CLI

SPREAD · tests

BUILT ON IT · CI integrations

FIRST BOOT · cloud-init changes

PKGPROXY · caching for guests

SNAP · snap-only features

CONTAINER · OCI image

NATIVE · packages

BUILD TIME · data and rules

1 / 1

Roads from here