openSUSE Leap and Tumbleweed
Leap 15, 16, Tumbleweed for users
image-garden has openSUSE Leap 15.4 to 16.1 and Tumbleweed on x86_64 and aarch64, all booting with EFI, from three places on download.opensuse.org, each checked against the .sha256 file beside it; an opensuse user, no apt or zypper setup from pkgproxy, and Fedora's EDK2 for Leap 15.4 and 15.5 on aarch64.
On the map: systems
▶ Watch this deck — 6 scenes, ~5 min
Worth seeing first
- The support matrix — where openSUSE sits among the other families
01 Leap and Tumbleweed
Twelve systems: Leap 15.4, 15.5, 15.6, 16.0, 16.1 and Tumbleweed, each on x86_64 and aarch64, all booting with EFI.
openSUSE gives you two ways to live. Leap is a release you can stay on for years; Tumbleweed rolls on, a little every day. image-garden has both: Leap 15.4, 15.5 and 15.6, Leap 16.0 and 16.1, and Tumbleweed, each for x86_64 and aarch64. That's twelve systems, and every one boots with EFI firmware. Our example is opensuse-cloud-16.0.x86_64. Next to ubuntu-cloud-24.04.x86_64 the name has the same shape, but a lot behind it differs: where the image comes from, how it's checked, and what pkgproxy can do for it. This deck walks through those, and what to keep in mind when you test on openSUSE.
Details and sources
Details
data/opensuse.inistarts with[META]:Group=opensuse,Variant=cloud(opensuse.ini:4-6), then twelve sections,opensuse-cloud-15.4toopensuse-cloud-16.1andopensuse-cloud-tumbleweed, each onx86_64andaarch64withBoot=efi(opensuse.ini:8-90).- The README lists "Leap 15.4, 15.5, 15.6, 16.0, 16.1, Tumbleweed" on x86_64 and aarch64 (README.md:664-667).
- That Leap is a fixed release with years of updates and Tumbleweed a rolling release is openSUSE's release model (derived).
Read more
02 Three places, one hash file each
Leap 15 from repositories/Cloud:/Images:/Leap_15.x, Leap 16 from distribution/leap/16.x/appliances, Tumbleweed from Virtualization:/Appliances:/Images:/openSUSE-Tumbleweed; each checked against IMAGE.sha256.
openSUSE's images come from three different places on download.opensuse.org, one per generation. Leap 15 images are built in the Open Build Service, in a project for cloud images, and image-garden takes their NoCloud flavour. Leap 16 images sit with the release itself, under distribution, leap, the version, then appliances, as the Minimal VM in its Cloud flavour. Tumbleweed comes from a project for virtualization appliances, with aarch64 in a repository of its own. Wherever it lives, each image has a small file beside it, the image's name plus .sha256, holding its hash. image-garden fetches that file too, and the image must match it before it's used.
Details and sources
Details
- Leap 15.4, 15.5 and 15.6:
https://download.opensuse.org/repositories/Cloud:/Images:/Leap_15.x/images/openSUSE-Leap-15.x.ARCH-NoCloud.qcow2(opensuse.ini:8-48). - Leap 16.0 and 16.1:
https://download.opensuse.org/distribution/leap/16.x/appliances/Leap-16.x-Minimal-VM.ARCH-Cloud.qcow2(opensuse.ini:50-76). NEWS records two fixes to the 16.0 URLs, the later one moving them from stale build files to the final release images (NEWS:229-231). - Tumbleweed:
https://download.opensuse.org/repositories/Virtualization:/Appliances:/Images:/openSUSE-Tumbleweed/openSUSE_Tumbleweed/openSUSE-Tumbleweed-Minimal-VM.x86_64-Cloud.qcow2, andopenSUSE_Tumbleweed_ARM/…aarch64-Cloud.qcow2for aarch64 (opensuse.ini:78-90). - Every section's
SHA256SUMS=is the image URL plus.sha256. A section withSHA256SUMS=getsdownload-with-sha256sums(rulegen.py:510-514), which saves the file asFILE.sha256sums, finds the hash by the file's name, and checks withsha256sum --check(image-garden:460-559, image-garden:75-92). - That "Open Build Service" builds the
repositories/trees, and what the NoCloud and Cloud flavours hold, is openSUSE's practice (derived).
Read more
03 What the first boot does on openSUSE
Users root/root and opensuse/opensuse, host name opensuse-16-0. With pkgproxy: /etc/hosts, snap setup and GOPROXY; nothing for zypper.
On its first boot openSUSE gets the common user-data, like everyone else: root with the password root, and a user called opensuse, password opensuse, with passwordless sudo. The host name is opensuse-16-0, as dots aren't allowed there. With pkgproxy in reach, though, there's less to do. openSUSE installs packages with zypper, not apt, and image-garden runs no setup for zypper, so packages come straight from openSUSE's mirrors, uncached. The http rewrite finds no apt directory and does nothing. What you do get is the pkgproxy name in /etc/hosts, the snap script, which prepares snapd for the proxy even before snapd is installed, and GOPROXY for the go command.
Details and sources
Details
- Users:
root/root, andopensuse/opensusein groupuserswithsudo: ["ALL=(ALL) NOPASSWD:ALL"]and bash (010-qemu.mk:200-211, rulegen.py:467). - Host name: dots and pluses become dashes, so release
16.0givesopensuse-16-0and Tumbleweedopensuse-tumbleweed(010-qemu.mk:94-104). - pkgproxy:
PKGPROXY_BOOTCMD_SETUPnamesaptonly fordebianandubuntu;PKGPROXY_RUNCMD_SETUPnamessnapfor every group butalpine(010-qemu.mk:127-130). bootcmd still adds/etc/hostsand probes pkgproxy (010-qemu.mk:156-162);GOPROXYgoes to/etc/environment(010-qemu.mk:170-180). - The snap script writes a systemd drop-in for snapd, also where snapd is installed later (proxy/README.md:175-180). Whether openSUSE's images ship snapd is not in the source (derived: they do not by default).
- The apt rewrite runs only
if [ -d /etc/apt ](010-qemu.mk:244). - No file under
mk/gives openSUSE a template; the only openSUSE entries inmk/are the aarch64 firmware list of the next scene and a comment on firmware paths (010-qemu-x86_64.mk:260).
04 Older Leap on 64-bit Arm
opensuse-cloud-15.4 and 15.5 on aarch64 are in GARDEN_AARCH64_FEDORA_EDK2_SYSTEMS and boot with Fedora's EDK2.
On 64-bit Arm, two of these systems need different firmware. Leap 15.4 and 15.5 have boot loaders older than what current EDK2 firmware enforces, and with the EDK2 that Debian and Ubuntu build, they stop with a Synchronous Exception before their kernel starts. So image-garden boots them with Fedora's build of EDK2, which works around such boot loaders. The snap carries it in its qemu-aarch64 component; other installs download it once, by its checksum, from image-garden's own project. You don't choose this: the list of systems is in the make files. The other openSUSE systems use the usual firmware. One more thing: image-garden's own tests on Arm cover Leap 15 and Tumbleweed, not Leap 16.
Details and sources
Details
GARDEN_AARCH64_FEDORA_EDK2_SYSTEMSlists ten systems, among themopensuse-cloud-15.4andopensuse-cloud-15.5; the comment above it gives the reason: boot loaders that "predate what newer EDK2 enforces", which stop with "Synchronous Exception" under the EDK2 Debian and Ubuntu build (010-qemu-aarch64.mk:114-145).- The snap uses the copy in its
qemu-aarch64component; elsewhere the code and vars files are downloaded withdownload-with-sha256sumfrom the project's generic packageedk2-aarch64-fedora(010-qemu-aarch64.mk:147-160). NEWS: "Older aarch64 systems boot again", openSUSE Leap 15.4 and 15.5 among them (NEWS:145-152). - The variable is set with
?=, so a project or the command line can change the list. - image-garden's CI job "aarch64: [opensuse]" tests
opensuse-cloud-15.4,15.5,15.6andtumbleweed, and may fail without failing the pipeline (.gitlab-ci.yml:881-887, .gitlab-ci.yml:636-652); the x86_64 job tests all six (.gitlab-ci.yml:803-809).
Read more
05 Worth knowing before you test on openSUSE
Tumbleweed's image name never changes: remove it and its .sha256sums file from the cache to update. zypper, not apt; SELinux on Leap 16, AppArmor on Leap 15.
A few things to keep in mind on openSUSE. Leap is a release: what you test today is what you get next month, plus updates. Tumbleweed rolls, and its image keeps one name while what's inside changes, so the copy in your cache stays on the day you first fetched it. Delete it, with its checksum file, to move on. Packages come from zypper, so a test script that calls apt-get won't get far; check for the package manager, not the distribution. Leap 16 uses SELinux where Leap 15 used AppArmor, so a test about confinement behaves differently from one to the other. And the older Leap 15 releases are past their end of life.
Details and sources
Details
- Tumbleweed's URL has no version or date:
openSUSE-Tumbleweed-Minimal-VM.x86_64-Cloud.qcow2(opensuse.ini:78-90), and so do the Leap 16 appliances. The helper fetches the checksum file and the image only when they are missing from the cache (image-garden:475-559);distcleanremoves the image but notFILE.sha256sums(rulegen.py:486-492). So the first download stays until both are removed from the cache'sopensuse/directory (derived from the code; the Debian deck walks through it). - image-garden configures nothing for zypper (010-qemu.mk:127-130); that openSUSE uses zypper is general knowledge (derived).
- Leap 16 uses SELinux by default where Leap 15 used AppArmor: openSUSE's release notes, not in the source (derived). Check with
getenforcein the guest. - That Leap 15.4 and 15.5 are past their end of life is openSUSE's lifecycle (derived); image-garden keeps them in
data/opensuse.iniand in its CI (.gitlab-ci.yml:803-809).
Read more
- Where image-garden keeps its files, Debian cloud images, Fedora cloud images, which also run SELinux.
06 Where to go from here
Next: UEFI firmware, the users, pkgproxy in the user-data, downloads, Debian and the support matrix.
So openSUSE is one file, Leap and Tumbleweed on two architectures, images from three places, and a first boot where pkgproxy has less to do. From here, the firmware deck shows what every system boots from, Fedora's EDK2 included. The users deck explains the root and opensuse accounts, and the pkgproxy deck shows what the proxy adds for each family. The download deck shows how the hash file and the image are checked, the Debian deck explains the cache catch with images that keep their name, and the support matrix sets openSUSE beside every other family.
Details and sources
Read more
- UEFI firmware per system, the users every system gets, what pkgproxy adds to user-data.
- Downloading and checking images, Debian cloud images, the support matrix.
- The other distribution decks: Fedora, Alpine, and the 64-bit Arm machine.
Read more
Basis of the statements on this page
Read in data/opensuse.ini, rulegen.py, mk/010-qemu.mk, mk/010-qemu-aarch64.mk, the image-garden script, proxy/README.md, README.md, NEWS and .gitlab-ci.yml of image-garden at the commit in garden.commit ("code"). openSUSE's release model, its package manager and its security modules are general knowledge ("derived"), as is the cache behaviour of images whose name does not change, worked out from the download helper. Nothing was run for this page.
Every openSUSE system
The system name is opensuse-cloud-RELEASE.ARCH. Every system boots with efi. The aarch64 firmware column says which EDK2 the aarch64 system boots with (UEFI firmware per system).
| System | Release | Architectures | Boot | Source | aarch64 firmware | Host name |
|---|---|---|---|---|---|---|
opensuse-cloud-15.4 | Leap 15.4 | x86_64, aarch64 | efi | Cloud:Images:Leap_15.4, NoCloud | Fedora's EDK2 | opensuse-15-4 |
opensuse-cloud-15.5 | Leap 15.5 | x86_64, aarch64 | efi | Cloud:Images:Leap_15.5, NoCloud | Fedora's EDK2 | opensuse-15-5 |
opensuse-cloud-15.6 | Leap 15.6 | x86_64, aarch64 | efi | Cloud:Images:Leap_15.6, NoCloud | usual | opensuse-15-6 |
opensuse-cloud-16.0 | Leap 16.0 | x86_64, aarch64 | efi | distribution/leap/16.0/appliances, Minimal-VM Cloud | usual | opensuse-16-0 |
opensuse-cloud-16.1 | Leap 16.1 | x86_64, aarch64 | efi | distribution/leap/16.1/appliances, Minimal-VM Cloud | usual | opensuse-16-1 |
opensuse-cloud-tumbleweed | Tumbleweed | x86_64, aarch64 | efi | Virtualization:Appliances:Images:openSUSE-Tumbleweed, Minimal-VM Cloud | usual | opensuse-tumbleweed |
Image URL patterns and checksum files
ARCH is x86_64 or aarch64, spelled the same way in the URLs. Every checksum file is the image URL with .sha256 appended: openSUSE's file with the image's hash, saved in the cache as FILE.sha256sums.
Leap 15.x: https://download.opensuse.org/repositories/Cloud:/Images:/Leap_15.x/images/openSUSE-Leap-15.x.ARCH-NoCloud.qcow2
Leap 16.x: https://download.opensuse.org/distribution/leap/16.x/appliances/Leap-16.x-Minimal-VM.ARCH-Cloud.qcow2
Tumbleweed: https://download.opensuse.org/repositories/Virtualization:/Appliances:/Images:/openSUSE-Tumbleweed/REPO/openSUSE-Tumbleweed-Minimal-VM.ARCH-Cloud.qcow2
REPO is openSUSE_Tumbleweed for x86_64, openSUSE_Tumbleweed_ARM for aarch64
SHA256SUMS: the image URL + .sha256
None of these names carries a build date, so a cached image stays until it and its .sha256sums file are removed (The same name every day shows how).
What the first boot does
| What | On openSUSE | Source |
|---|---|---|
| Users | root/root; opensuse/opensuse in group users, passwordless sudo, bash | 010-qemu.mk:200-211 |
| Host name | opensuse-RELEASE with dots as dashes, such as opensuse-16-0 | 010-qemu.mk:94-104 |
| SSH | password logins, root may log in | 010-qemu.mk:212-243 |
| apt sources | nothing: there is no /etc/apt | 010-qemu.mk:244 |
| pkgproxy, bootcmd | /etc/hosts entry and reachability probe; no 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 |
| zypper | nothing: packages come from openSUSE's mirrors | 010-qemu.mk:127-130 |
| Distribution quirks | none in the user-data; Fedora's EDK2 for 15.4 and 15.5 on aarch64 | 010-qemu-aarch64.mk:134-145 |
Running an openSUSE system
$ image-garden make opensuse-cloud-16.0.x86_64.run $ ./opensuse-cloud-16.0.x86_64.run --query
In spread.yaml the systems are opensuse-cloud-15.4 to opensuse-cloud-tumbleweed, with username: opensuse and password: opensuse, as in image-garden's spread demo (spread-demo/spread.yaml:262-280).
Roads from here
SYSTEMS · distributions
- Debian cloud images — the daily-image cache catch, explained for Debian
- The support matrix — every family and architecture side by side
ARCHITECTURES · machines and firmware
- UEFI firmware per system — the firmware every system boots from, Fedora's EDK2 included
RUNTIME · make rules and the CLI
- Downloading and checking images — how the checksum file and the image are fetched and checked
FIRST BOOT · cloud-init changes
- The users every system gets — the root and opensuse accounts every system gets
PKGPROXY · caching for guests
- What pkgproxy adds to user-data — what pkgproxy adds to the first boot, and for which families