Debian cloud images
10 to 14, sid for users
image-garden has Debian 10 to 14 and sid on x86_64 and aarch64, all booting with EFI, from the daily genericcloud images on cloud.debian.org checked against Debian's SHA512SUMS; the first boot gives a debian user, and with pkgproxy apt, snap and GOPROXY setup as on Ubuntu.
On the map: systems
▶ Watch this deck — 6 scenes, ~5 min
Worth seeing first
- The support matrix — where Debian sits among the other families
01 Six Debian releases
Twelve systems: Debian 10 to 14 and sid, each on x86_64 and aarch64, all booting with EFI.
Ubuntu is built from Debian, but your users on Debian run different versions of almost everything, so it's worth testing both. image-garden has six Debian releases: 10, 11, 12 and 13, then 14, which Debian calls forky and which is still testing, and sid, the unstable branch. Each one comes for x86_64 and aarch64, which makes twelve systems, and every one of them boots with EFI firmware. Our example here is debian-cloud-13.x86_64. Next to ubuntu-cloud-24.04.x86_64 the name has the same shape: a group, a release, an architecture. This deck shows where its image comes from, what its first boot does, and what to watch for.
Details and sources
Details
data/debian.inistarts with[META]:Group=debian,Variant=cloud(debian.ini:4-6), then twelve sections under the codename commentsbuster,bullseye,bookworm,trixie,forkyandsid, each withArch=x86_64orArch=aarch64,Boot=efiandRelease=10 to 14 orsid(debian.ini:8-103).- The README lists "10 (Buster), 11 (Bullseye), 12 (Bookworm), 13 (Trixie), 14 (Forky, daily images), Sid" on x86_64 and aarch64 (README.md:637-641); NEWS calls 14 "forky, currently testing" (NEWS:131-132).
- The README and the manual page use
debian-cloud-13.x86_64as their example (README.md:557). - That Ubuntu is built from Debian, and that sid is Debian's unstable branch, is general Debian knowledge (derived).
Read more
02 The daily image and SHA512SUMS
…/images/cloud/trixie/daily/latest/debian-13-genericcloud-amd64-daily.qcow2, checked with SHA-512 against the SHA512SUMS list in the same directory.
Debian publishes its cloud images on cloud.debian.org, and image-garden takes the daily build of each release. Look at the URL for our example. First the codename, trixie, then daily, then latest, then a file named for the release and the architecture, with the architecture spelled amd64, the way Debian spells it. It's the genericcloud image, made for virtual machines; only Debian 10 uses the plain generic one. In the same directory sits SHA512SUMS, Debian's list of checksums for every file there. image-garden fetches that list first and finds the line for this file. Then it downloads the image and checks it against that line.
Details and sources
Details
- Every Debian section uses
https://cloud.debian.org/images/cloud/CODENAME/daily/latest/withSHA512SUMS=theSHA512SUMSfile of the same directory; the example is debian.ini:59-64. - Debian 10 uses
debian-10-generic-amd64-daily.qcow2anddebian-10-generic-arm64-daily.qcow2(debian.ini:10-23); 11 to sid usegenericcloud(debian.ini:27-103). That genericcloud is the smaller image for virtual machines and generic the one with drivers for real hardware is Debian's description (derived). - A section with
SHA512SUMS=gets a rule that runsimage-garden download-with-sha512sums(rulegen.py:498-502). The helper fetches the list toFILE.sha512sums, looks up the file's line, downloads the image (through pkgproxy first, by its hash, when there is one) and checks it withsha512sum --check; on a mismatch it deletes both and tries once more (image-garden:358-458). It readsHASH NAME,HASH *NAMEand BSD-style lines (image-garden:75-92). - image-garden's own name for Debian's architectures:
map_to_debian_archmapsx86_64toamd64andaarch64toarm64(000-garden.mk:27-30), used for Ubuntu Core; the Debian URLs spell them out. - rulegen.py rejects an
x86_64section whose URL has neitherx86_64noramd64, and anaarch64one withoutaarch64orarm64(rulegen.py:406-416).
Read more
03 What the first boot does on Debian
Users root/root and debian/debian, host name debian-13, apt sources over http. With pkgproxy: apt setup in bootcmd, snap setup in runcmd, GOPROXY.
On its first boot, cloud-init treats Debian the way it treats Ubuntu. You get root, password root, and a user named debian, password debian, with passwordless sudo. The host name is debian-13. Every apt source file, the older .list kind and the newer .sources kind, is switched from https to http, so that a caching proxy can see the downloads. With a pkgproxy in reach, there's more. Early on, pkgproxy's apt script points apt at the cache, so even cloud-init's own package installs are cached. At the end, the snap script prepares snapd for the proxy, even if you install snapd later. And /etc/environment gets GOPROXY for the go command.
Details and sources
Details
- The common user-data creates
rootwithplain_text_passwd: rootand the group's user,debian, with the passworddebian,groups: users,sudo: ["ALL=(ALL) NOPASSWD:ALL"]andshell: /bin/bash(010-qemu.mk:200-211); the group is passed as the user name (rulegen.py:467). - The host name is the group and release with dots and pluses turned into dashes:
debian-13,debian-sid(010-qemu.mk:94-104, 010-qemu.mk:196). - Every system's
runcmdswitcheshttps://tohttp://in/etc/apt's*.listand*.sourcesfiles, when/etc/aptexists (010-qemu.mk:244). - With a pkgproxy:
PKGPROXY_BOOTCMD_SETUPisaptfor the groupsdebianandubuntu,PKGPROXY_RUNCMD_SETUPissnapfor every group butalpine(010-qemu.mk:127-130);GOPROXY="http://pkgproxy:PORT/go,direct"is appended to/etc/environment(010-qemu.mk:170-180). - The apt script writes
Acquire::http::Proxyto/etc/apt/apt.conf.d/99pkgproxy; the snap script writes a systemd drop-in for snapd "also where snapd is installed later", and restarts snapd where it is installed (proxy/README.md:166-184). Whether Debian's cloud images ship snapd is not in the source; Debian does not install it by default (derived). - No file under
mk/names Debian: it has no template of its own, and the apt hook inmk/050-ubuntu.mkemits nothing for the groupdebian(050-ubuntu.mk:14-28).
04 The same name every day
The cached debian-13-genericcloud-amd64-daily.qcow2 is kept until you delete it. Remove it together with its .sha512sums file to get a newer daily image.
Here's a catch with daily images. The file's name ends in daily, and tomorrow's has exactly the same name, with different contents. image-garden keeps the image in your download cache under that name, and once it's there and matches the checksum list saved beside it, there's nothing more to fetch. So your debian-cloud-13 stays on the day you first downloaded it, which is good for repeatable tests. When you want a newer one, distclean removes the image but keeps that saved list. The old list then costs a second download, or, through pkgproxy, brings the old image back. So delete both from the cache's debian directory, and the next make fetches today's.
Details and sources
Details
- The local file name is the URL's last part,
debian-13-genericcloud-amd64-daily.qcow2, in$(GARDEN_DL_DIR)/debian/, with the system's linkdebian-cloud-13.x86_64.qcow2beside it (rulegen.py:498-502). The download directory is~/.cache/image-garden/dlfor a native install; see where image-garden keeps its files. - The helper fetches the list only when
FILE.sha512sumsis missing, and the image only whenFILEis missing; otherwise it only checks the image against the saved list (image-garden:373-458). distcleanremoves the downloaded image, the link,.urland.filename(rulegen.py:486-492), notFILE.sha512sums. With the old list kept, the next download asks pkgproxy for the old hash first (image-garden:281-308); a pkgproxy that kept the old image gives it back and the check passes. Without one, the new image fails the old hash, both files are deleted, and the second attempt fetches a fresh list and downloads again (image-garden:440-456). Worked out from the code (derived), not run.- To move to today's image: remove
debian-13-genericcloud-amd64-daily.qcow2anddebian-13-genericcloud-amd64-daily.qcow2.sha512sumsfrom the cache'sdebian/directory, then runimage-garden make debian-cloud-13.x86_64.run; the newer base image makes make prepare the disk again (derived). - The same holds for every Debian release, and for any image whose name does not change upstream (derived).
05 Worth knowing before you test on Debian
sid and 14 (testing) change daily. .sources files are rewritten to http like .list files. Debian 10 gets no archive rewrite: add one with EXTRA_CLOUD_INIT_APT_CONFIG if you need it.
A few things are worth knowing before you test on Debian. Sid and 14 move under you. Debian's unstable and testing branches change every day, so a test that passed last week can fail on a fresh image for reasons that aren't yours. Keep the cached image while you chase a failure. Newer releases describe their apt sources in the deb822 format, in a file called debian.sources, and image-garden's http rewrite covers those too. And Debian 10 is past the end of its support. Unlike old Ubuntu releases, nothing in image-garden points its apt at an archive server. If its packages have moved, give apt new sources with the apt hook.
Details and sources
Details
debian-cloud-14(forky) anddebian-cloud-siduse daily images like the others (debian.ini:73-103); NEWS calls 14 "currently testing" (NEWS:131-132). That testing and unstable change daily and can break is Debian's release model (derived).- The
runcmdrewrite covers*.sourcesas well as*.list(010-qemu.mk:244). That newer Debian releases use deb822debian.sourcesfiles, and what such a file holds, is Debian's practice (derived); the drawing's file is an illustration. - Ubuntu's archive rewrite is only for the group
ubuntuand the releases on its list (050-ubuntu.mk:12-28); the common template calls the hookEXTRA_CLOUD_INIT_APT_CONFIGwith the group and release for every system (010-qemu.mk:198), so a project can define it fordebianand10, keeping Ubuntu's block as the hooks deck shows. - That Debian 10 is past its long-term support, and that Debian moves the packages of such releases to archive.debian.org, is Debian's practice (derived); check the guest's
apt updatebefore relying on it.
Read more
06 Where to go from here
Next: Ubuntu cloud images, the users, pkgproxy in the user-data, downloads, cloud-init hooks and the support matrix.
So Debian is one file, six releases on two architectures, daily images checked against Debian's own list, and a first boot much like Ubuntu's. From here, the Ubuntu deck shows the other apt family, and the archive rewrite that Debian doesn't get. The users deck explains the root and debian accounts, and the pkgproxy deck goes through what the proxy adds to the first boot. The download deck shows how the list and the image are fetched and checked, the hooks deck how to change the first boot, and the support matrix sets Debian beside every other family.
Details and sources
Read more
- Ubuntu cloud images, the users every system gets, what pkgproxy adds to user-data.
- Downloading and checking images, changing what cloud-init does, the support matrix.
- The other distribution decks: Fedora, openSUSE, Alpine, and the 64-bit Arm machine.
Read more
Basis of the statements on this page
Read in data/debian.ini, rulegen.py, mk/010-qemu.mk, the image-garden script, proxy/README.md, README.md and NEWS of image-garden at the commit in garden.commit ("code"). What Debian's branches are, how its images differ and where its archived releases go is Debian's practice ("derived"). The cache behaviour of daily images is worked out from the download helper ("derived"). Nothing was run for this page.
Every Debian system
The system name is debian-cloud-RELEASE.ARCH. Every system boots with efi: from its own copies of the host's EDK2 firmware (UEFI firmware per system).
| System | Codename | Architectures | Boot | Image | Host name |
|---|---|---|---|---|---|
debian-cloud-10 | buster | x86_64, aarch64 | efi | generic | debian-10 |
debian-cloud-11 | bullseye | x86_64, aarch64 | efi | genericcloud | debian-11 |
debian-cloud-12 | bookworm | x86_64, aarch64 | efi | genericcloud | debian-12 |
debian-cloud-13 | trixie | x86_64, aarch64 | efi | genericcloud | debian-13 |
debian-cloud-14 | forky | x86_64, aarch64 | efi | genericcloud | debian-14 |
debian-cloud-sid | sid | x86_64, aarch64 | efi | genericcloud | debian-sid |
Image URL and checksum list
Every image comes from Debian's daily builds; CODENAME is the codename in the table, R the release, DARCH Debian's name for the architecture (amd64 for x86_64, arm64 for aarch64), and KIND is generic for Debian 10 and genericcloud for the others.
image https://cloud.debian.org/images/cloud/CODENAME/daily/latest/debian-R-KIND-DARCH-daily.qcow2 checksum https://cloud.debian.org/images/cloud/CODENAME/daily/latest/SHA512SUMS
The checksum list is Debian's SHA512SUMS for the whole directory, checked with download-with-sha512sums. It is saved in the cache as FILE.sha512sums beside the image, and both keep the upstream name, which is the same every day: the first download stays until you remove both (The same name every day).
What the first boot does
| What | On Debian | Source |
|---|---|---|
| Users | root/root; debian/debian in group users, passwordless sudo, bash | 010-qemu.mk:200-211 |
| Host name | debian-RELEASE, such as debian-13 | 010-qemu.mk:94-104 |
| SSH | password logins, root may log in | 010-qemu.mk:212-243 |
| apt sources | https:// becomes http:// in *.list and *.sources | 010-qemu.mk:244 |
| pkgproxy, bootcmd | /etc/hosts entry, reachability probe, pkgproxy's apt setup script | 010-qemu.mk:127-162 |
| pkgproxy, runcmd | /etc/hosts entry again, pkgproxy's snap setup script | 010-qemu.mk:164-168 |
| pkgproxy, files | GOPROXY appended to /etc/environment | 010-qemu.mk:170-180 |
| Distribution quirks | none: no mk/ file or template names Debian | per-distro quirks |
Running a Debian system
$ image-garden make debian-cloud-13.x86_64.run $ ./debian-cloud-13.x86_64.run --query $ image-garden allocate debian-cloud-13.x86_64
In spread.yaml the system is debian-cloud-13, with username: debian and password: debian, as in image-garden's spread demo (spread-demo/spread.yaml:42-60).
Roads from here
SYSTEMS · distributions
- Ubuntu cloud images — the other apt family, and the archive rewrite Debian does not get
- The support matrix — every family and architecture side by side
RUNTIME · make rules and the CLI
- Downloading and checking images — how the checksum list and the image are fetched and checked
FIRST BOOT · cloud-init changes
- The users every system gets — the root and debian accounts every system gets
- Changing what cloud-init does — the apt hook and other ways to change the first boot
PKGPROXY · caching for guests
- What pkgproxy adds to user-data — what pkgproxy adds to the first boot, line by line