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

01 Leap and Tumbleweed

OPENSUSE CLOUD IMAGES Leap: a release you stay on Tumbleweed: rolls on every day Leap 15.4 Leap 15.5 Leap 15.6 Leap 16.0 Leap 16.1 Tumbleweed x86_64 aarch64 12 systems efi efi efi efi efi efi efi efi efi efi efi efi every one boots with EFI firmware efi opensuse-cloud-16.0.x86_64 ubuntu-cloud-24.04.x86_64 group-variant-release.arch where the image comes from how it is checked what pkgproxy can do
openSUSE Leap, a release you stay on, and Tumbleweed, which rolls on every day: Leap 15.4, 15.5, 15.6, 16.0, 16.1 and Tumbleweed, each on x86_64 and aarch64, twelve systems, all booting with EFI. opensuse-cloud-16.0.x86_64 has the same shape as ubuntu-cloud-24.04.x86_64. The deck covers where the images come from, how they are checked and what pkgproxy does

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.ini starts with [META]: Group=opensuse, Variant=cloud (opensuse.ini:4-6), then twelve sections, opensuse-cloud-15.4 to opensuse-cloud-16.1 and opensuse-cloud-tumbleweed, each on x86_64 and aarch64 with Boot=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).

02 Three places, one hash file each

THREE PLACES https://download.opensuse.org/ Leap 15 repositories/Cloud:/Images:/Leap_15.6/images/ openSUSE-Leap-15.6.x86_64-NoCloud.qcow2 Leap 16 distribution/leap/16.0/appliances/ Leap-16.0-Minimal-VM.x86_64-Cloud.qcow2 Tumbleweed repositories/Virtualization:/Appliances:/Images:/openSUSE-Tumbleweed/ openSUSE_Tumbleweed/openSUSE-Tumbleweed-Minimal-VM.x86_64-Cloud.qcow2 aarch64: from openSUSE_Tumbleweed_ARM/ …/appliances/Leap-16.0-Minimal-VM.x86_64-Cloud.qcow2.sha256 the image must match the hash in its .sha256 file before use
openSUSE images come from three places on download.opensuse.org: Leap 15 from the Open Build Service project Cloud:Images:Leap_15.x as NoCloud images, Leap 16 from distribution/leap/16.x/appliances as Minimal-VM Cloud images, Tumbleweed from the Virtualization:Appliances:Images:openSUSE-Tumbleweed project, with aarch64 in openSUSE_Tumbleweed_ARM. Each image has a .sha256 file beside it, which image-garden fetches too, and the image is checked against it before use

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, and openSUSE_Tumbleweed_ARM/…aarch64-Cloud.qcow2 for aarch64 (opensuse.ini:78-90).
  • Every section's SHA256SUMS= is the image URL plus .sha256. A section with SHA256SUMS= gets download-with-sha256sums (rulegen.py:510-514), which saves the file as FILE.sha256sums, finds the hash by the file's name, and checks with sha256sum --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).

03 What the first boot does on openSUSE

FIRST BOOT root / root opensuse / opensuse passwordless sudo opensuse-16-0 host name: no dots with a pkgproxy in reach not set up set up zypper: no setup script packages come straight from the mirrors, uncached http rewrite: no /etc/apt, nothing /etc/hosts: the name pkgproxy snap setup: snapd ready, even if added later GOPROXY in /etc/environment
openSUSE gets root with password root and opensuse with password opensuse and passwordless sudo, host name opensuse-16-0. With a pkgproxy in reach it gets no setup for zypper, so packages come uncached, and the apt rewrite finds no /etc/apt; it does get the pkgproxy entry in /etc/hosts, the snap setup, which prepares snapd even before it is installed, and GOPROXY

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, and opensuse/opensuse in group users with sudo: ["ALL=(ALL) NOPASSWD:ALL"] and bash (010-qemu.mk:200-211, rulegen.py:467).
  • Host name: dots and pluses become dashes, so release 16.0 gives opensuse-16-0 and Tumbleweed opensuse-tumbleweed (010-qemu.mk:94-104).
  • pkgproxy: PKGPROXY_BOOTCMD_SETUP names apt only for debian and ubuntu; PKGPROXY_RUNCMD_SETUP names snap for every group but alpine (010-qemu.mk:127-130). bootcmd still adds /etc/hosts and probes pkgproxy (010-qemu.mk:156-162); GOPROXY goes 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 in mk/ 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

OLDER LEAP ON 64-BIT ARM opensuse-cloud-15.4.aarch64 opensuse-cloud-15.5.aarch64 EDK2 as Debian and Ubuntu build it Synchronous Exception Fedora's build of EDK2 the kernel starts the snap: its qemu-aarch64 component elsewhere: downloaded once, by checksum GARDEN_AARCH64_FEDORA_EDK2_SYSTEMS ?= almalinux-cloud-8 … fedora-cloud-38 opensuse-cloud-15.4 opensuse-cloud-15.5 oracle-cloud-8 … Leap 15.6, 16.0, 16.1 and Tumbleweed: the usual firmware image-garden's own Arm tests: Leap 15 and Tumbleweed, not Leap 16
opensuse-cloud-15.4.aarch64 and opensuse-cloud-15.5.aarch64 stop with a Synchronous Exception under the EDK2 Debian and Ubuntu build, so image-garden boots them with Fedora's EDK2: the snap's qemu-aarch64 component carries it, other installs download it once by checksum. The list GARDEN_AARCH64_FEDORA_EDK2_SYSTEMS names them; the other openSUSE systems use the usual firmware. image-garden's Arm tests cover Leap 15 and Tumbleweed, not Leap 16

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_SYSTEMS lists ten systems, among them opensuse-cloud-15.4 and opensuse-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-aarch64 component; elsewhere the code and vars files are downloaded with download-with-sha256sum from the project's generic package edk2-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.6 and tumbleweed, 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).

05 Worth knowing before you test on openSUSE

WORTH KNOWING Leap a release: next month's image is today's, plus updates Tumbleweed openSUSE-Tumbleweed-Minimal-VM.x86_64-Cloud.qcow2 one name, new contents: the cached copy stays on its first day delete it and its .sha256sums file to move on zypper $ sudo apt-get install … check for the package manager Leap 15: AppArmor Leap 16: SELinux a test about confinement behaves differently the older Leap 15 releases are past their end of life
On openSUSE: Leap is a release; Tumbleweed's image keeps one name while its contents change, so the cached copy stays until you delete it and its .sha256sums file; packages come from zypper, not apt, so check for the package manager; Leap 16 uses SELinux where Leap 15 used AppArmor; the older Leap 15 releases are past their end of life

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); distclean removes the image but not FILE.sha256sums (rulegen.py:486-492). So the first download stays until both are removed from the cache's opensuse/ 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 getenforce in 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.ini and in its CI (.gitlab-ci.yml:803-809).

06 Where to go from here

ROADS openSUSE UEFI firmware Fedora's EDK2 included The users root and opensuse pkgproxy in user-data what each family gets Downloads the hash file and the image Debian cloud images images that keep their name The support matrix every family side by side
Roads from openSUSE Leap and Tumbleweed: UEFI firmware, the users, pkgproxy in the user-data, downloads, Debian cloud images and the support matrix

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

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).

SystemReleaseArchitecturesBootSourceaarch64 firmwareHost name
opensuse-cloud-15.4Leap 15.4x86_64, aarch64efiCloud:Images:Leap_15.4, NoCloudFedora's EDK2opensuse-15-4
opensuse-cloud-15.5Leap 15.5x86_64, aarch64efiCloud:Images:Leap_15.5, NoCloudFedora's EDK2opensuse-15-5
opensuse-cloud-15.6Leap 15.6x86_64, aarch64efiCloud:Images:Leap_15.6, NoCloudusualopensuse-15-6
opensuse-cloud-16.0Leap 16.0x86_64, aarch64efidistribution/leap/16.0/appliances, Minimal-VM Cloudusualopensuse-16-0
opensuse-cloud-16.1Leap 16.1x86_64, aarch64efidistribution/leap/16.1/appliances, Minimal-VM Cloudusualopensuse-16-1
opensuse-cloud-tumbleweedTumbleweedx86_64, aarch64efiVirtualization:Appliances:Images:openSUSE-Tumbleweed, Minimal-VM Cloudusualopensuse-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

WhatOn openSUSESource
Usersroot/root; opensuse/opensuse in group users, passwordless sudo, bash010-qemu.mk:200-211
Host nameopensuse-RELEASE with dots as dashes, such as opensuse-16-0010-qemu.mk:94-104
SSHpassword logins, root may log in010-qemu.mk:212-243
apt sourcesnothing: there is no /etc/apt010-qemu.mk:244
pkgproxy, bootcmd/etc/hosts entry and reachability probe; no setup script010-qemu.mk:127-162
pkgproxy, runcmd/etc/hosts entry again, pkgproxy's snap setup script010-qemu.mk:164-168
pkgproxy, filesGOPROXY appended to /etc/environment010-qemu.mk:170-180
zyppernothing: packages come from openSUSE's mirrors010-qemu.mk:127-130
Distribution quirksnone in the user-data; Fedora's EDK2 for 15.4 and 15.5 on aarch64010-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

ARCHITECTURES · machines and firmware

RUNTIME · make rules and the CLI

FIRST BOOT · cloud-init changes

PKGPROXY · caching for guests