Linux

openSUSE Leap 16.1: Immutable Mode Joins Traditional Installs

openSUSE Leap 16.1 lets you choose traditional or immutable installs, replaces Leap Micro, and ships PHP 8.5, MariaDB 12.3 and…

5 November 2026  ·  4 min read  ·  Anand

openSUSE Leap 16.1: Immutable Mode Joins Traditional Installs

The openSUSE project released Leap 16.1 on November 3, 2026. It is the first minor release in the Leap 16 series, and its biggest change is about how you install and maintain a system, not about which packages it ships. Every Leap install can now run either as a traditional, package-managed system or as an immutable system with a read-only root filesystem and transactional updates. Until now the immutable approach was only available in the separate Leap Micro distribution. Leap Micro has now been merged into Leap, and there will be no Leap Micro 6.3 or 7.0.

One distribution, two ways to run it

You choose the mode in the Agama installer, now at version 24. Both modes use the same release, the same support lifecycle and the same maintenance updates, so choosing immutable no longer means following a separate product with its own schedule.

  • Traditional mode works the way Leap always has. You install and update packages with zypper on a writable root filesystem. This is the natural choice for cPanel-style hosting stacks, hand-tuned web servers and anything that expects to write to /usr.
  • Immutable Mode keeps the root filesystem read-only. Every update is applied to a new snapshot that becomes active at the next reboot, and you can return to an earlier snapshot if something goes wrong. Extra software runs in containers with Podman or Distrobox, or as Flatpaks on desktops.

Immutable Mode works well for container hosts, edge boxes, appliances and fleets of identical VMs, where a predictable base system and easy rollback matter more than installing packages by hand. openSUSE expects Tumbleweed to offer the same choice once Agama becomes its default installer.

What ships in Leap 16.1

Component Version
Linux kernel 6.12
systemd / glibc 257 / 2.40
Python 3.13 default, 3.14 available
PHP 8.5.12
MariaDB 12.3
PostgreSQL 18
LLVM 21
Podman 5.8
QEMU / libvirt 11.0 / 12.4

For web hosting this is a current stack: PHP 8.5, MariaDB 12.3 and PostgreSQL 18 are all available from the main repositories. On the desktop side, the release ships KDE Plasma 6.6, GNOME 48 (bug fixes only), Xfce 4.20 on Wayland and LXQt 2.4.

What changes for existing setups

  • SELinux is the default security module. If you are coming from older Leap releases that used AppArmor, test custom services, non-standard document roots and unusual ports before you move production traffic.
  • The CPU must support x86-64-v2. Very old hardware is no longer supported. openSUSE suggests Slowroll or Tumbleweed for those machines.
  • 32-bit (ia32) support is off by default. You can turn it back on if you need it, for example for Steam.
  • Leap Micro users move to Leap 16.1 in Immutable Mode. openSUSE does not plan any more Micro releases.
  • Release cadence: a new minor release is planned every year until Leap 16.6 in 2031.

To check whether an x86 machine meets the CPU baseline, ask the dynamic loader:

/lib64/ld-linux-x86-64.so.2 --help | grep x86-64-v2

If the output contains supported, the CPU is compatible.

Upgrading and trying it

From Leap 16.0

openSUSE’s official instructions are on the SDB:System_upgrade wiki page. On a typical server whose repositories use the $releasever variable (check with zypper lr -u), the in-place upgrade looks like this:

sudo zypper refresh && sudo zypper update
sudo zypper --releasever=16.1 refresh
sudo zypper --releasever=16.1 dup
sudo reboot

Take a snapshot or a full backup first, and disable any third-party repositories that do not yet have 16.1 builds.

From Leap Micro 6.2

Use the openSUSE Migration tool (opensuse-migration-tool on GitHub) to move to Leap 16.1 in Immutable Mode. openSUSE calls this path experimental, so back up before you start.

Day-to-day in Immutable Mode

Leap uses the transactional-update tooling from Leap Micro. Changes go into a new snapshot and take effect after a reboot:

sudo transactional-update up              # apply updates to a new snapshot
sudo transactional-update pkg install htop
sudo reboot
sudo snapper list                         # find a known-good snapshot
sudo transactional-update rollback 42     # make snapshot 42 the default

Before moving production

  • Check for known issues on the openSUSE:Known_bugs_16.1 wiki page.
  • Confirm that your control panel, backup agent and monitoring agent support Leap 16.1 and SELinux.
  • Test PHP 8.5 compatibility for your applications, and plan a dump and restore if you are moving between major PostgreSQL versions.
  • Decide per role whether a server should run traditional or immutable. Container hosts are the easiest place to start.

How TechProvidence can help

An in-place distribution upgrade or a move to an immutable base system is easy to get wrong on a busy production server. TechProvidence plans and carries out Linux upgrades and migrations, tests hosting stacks against new PHP and database versions, writes SELinux policy for custom services, and manages servers once they are running. If you are weighing Leap 16.1 for your infrastructure, contact us.

Source: LWN.net

Running into something similar?

We look after Linux servers, control panels and virtualization for businesses every day. If an update, vulnerability or outage here affects you, we can help.