Why openSUSE for a home server, not Ubuntu or Debian?

What openSUSE does well on a server

• Rollbacks are built in. The default install puts the root file system on btrfs and runs snapper. zypper takes a snapshot before and after every transaction, and the boot menu lists older snapshots. A broken update means "reboot into yesterday", not "restore from backup". The snapper rollback guide shows the steps.
• zypper is fast and strict. Its dependency solver (libsolv) tells you exactly what it wants to change and asks before it removes anything. Compared with apt it feels chatty at first; that chattiness is what saves you from surprises.
• Tested rolling releases. Every Tumbleweed snapshot runs through openQA, an automated test farm that installs and boots it in many configurations before it reaches you.
• podman and systemd are first-class. openSUSE ships podman, netavark and passt from its main repositories, in versions close to upstream on Tumbleweed. Rootless containers run by systemd (quadlets) work without third-party repos.
• The Open Build Service. OBS builds packages for openSUSE (and other distributions) from source. Need a newer tool than the main repo has? There is usually a devel project for it. Treat personal home: repositories with the same caution as a random PPA.
• Immutable variants when you want them. Leap Micro and the transactional server role update into a new snapshot with transactional-update, leaving the running system untouched until the next reboot.

Where it is weaker

• Smaller community. Search an error message and the top answers are for Ubuntu. They usually still help, but you translate apt to zypper and ufw to firewall-cmd yourself.
• Different package names. The web server is apache2, not httpd; headers packages end in -devel, not -dev. zypper se -s name finds them.
• Vendor software targets .deb first. Some projects publish an apt repository and nothing else. In practice that matters less on a server where almost everything runs as a container.
• Shorter support per Leap release than Ubuntu LTS. Plan a Leap minor-version upgrade roughly once a year; Ubuntu LTS and Debian stable let you wait longer.
• Security modules changed recently. New Tumbleweed installs use SELinux by default since February 2025 (openSUSE News), and Leap 16.0 ships with SELinux as its security module, with AppArmor as an option you can select after installation (Leap 16.0 release announcement). Older installs keep AppArmor. Many openSUSE forum answers still assume AppArmor. The AppArmor and SELinux guide sorts this out.

openSUSE, Ubuntu, Debian and Fedora side by side

Nothing here is a knockout. If you already know apt well, Debian is a fine server. The reason to pick openSUSE is the combination of snapshots you get for free and a container stack that does not lag behind.

Where those numbers come from, asked of each package manager on the same morning:

$ zypper --no-refresh info podman
Information for package podman:
-------------------------------
Repository     : Main Repository (OSS)
Name           : podman
Version        : 6.0.2-1.1
Arch           : x86_64
Vendor         : openSUSE
Installed Size : 55.1 MiB
Installed      : Yes
Status         : up-to-date
Source package : podman-6.0.2-1.1.src
Upstream URL   : https://github.com/containers/podman
Summary        : Daemon-less container engine for managing containers, pods and images

# Fedora 44
$ dnf -q repoquery --latest-limit 1 --qf '%{name}-%{version}-%{release}\n' podman
podman-5.8.7-1.fc44
# Debian 12
$ apt-cache policy podman | head -3
podman:
  Installed: (none)
  Candidate: 4.3.1+ds1-8+deb12u1+b3

Leap or Tumbleweed?

The general trade-off is in rolling versus fixed releases. For a home server it boils down to this:

• Leap 16 if you want to install, apply patches and not think about it for a year. Package versions stay put; only fixes arrive. Leap 15.6 is at the end of its life, so new installs should start on Leap 16.
• Tumbleweed if you want the newest podman, kernel and systemd, and you are fine running sudo zypper dup every week or two and reading what it proposes. Snapper is your safety net.

Every guide in this series notes where the two differ. Most of the time they do not.

When to pick something else

• A vendor you depend on only supports Ubuntu or RHEL, and you want their support.
• You want the largest pool of copy-paste answers while you learn: Ubuntu or Debian.
• You want five years on one release without a single upgrade: Ubuntu LTS or Debian.

Coming from docker-compose tutorials? The distribution matters less than you think: the compose to quadlet converter turns a compose file into systemd units that run the same on openSUSE, Fedora or Debian. Next in this series: installing openSUSE and the first ten minutes.

Frequently asked questions