Ubuntu 26.04 LTS is out: what does it bring for servers?

Yesterday, on 23 April 2026, Ubuntu 26.04 LTS was released, codenamed “Resolute Raccoon”. This is Ubuntu’s next long-term support (LTS) release: standard security support lasts five years, until 2031, with an Ubuntu Pro subscription until 2036, and with the Legacy add-on until 2041. In this article we look at what changes from a server operations point of view, and when it makes sense to upgrade.

The main changes in Ubuntu 26.04 LTS

The release notes include a separate summary for those coming from the previous LTS, 24.04. On a server, these matter most:

Component Ubuntu 24.04 LTS Ubuntu 26.04 LTS
Linux kernel (GA) 6.8 7.0
systemd 255 259
OpenSSH 9.6p1 10.2p1
APT 2.7 3.1
Netplan 1.0 1.2
Python 3.12 3.14
PHP 8.3 8.5
PostgreSQL 16 18
MySQL 8.0 8.4 LTS
OpenJDK (default) 21 25
Go 1.22 1.25

sudo-rs and coreutils written in Rust

The most noticeable change is that the sudo command is now provided by default by sudo-rs, a rewrite in Rust. The original sudo is still available as sudo.ws, but the sudo-ldap package has been dropped. Similarly, the basic command-line tools (ls, cat, sort and the rest) are provided by the Rust-based rust-coreutils; the GNU versions can be installed with a gnu prefix, and cp, mv and rm still come from the GNU package for now.

In everyday use you will hardly notice any of this. But if you run old scripts that lean heavily on rarely used options or output formats of the GNU tools, test them before you upgrade.

Time synchronisation: chrony, with NTS

On new installations the clock is synchronised by chrony instead of systemd-timesyncd, with NTS (Network Time Security) by default, that is, with authenticated time sources. This doesn’t happen automatically on upgraded machines; if you want chrony there too:

sudo apt-mark auto systemd-timesyncd
sudo apt install chrony

OpenSSH 10.2: goodbye to DSA

OpenSSH 10.2 uses hybrid, quantum-resistant key exchange by default, and no longer supports DSA keys at all. If there is still an ssh-dss key somewhere in an authorized_keys file or in an old automated process, it will stop working after the upgrade. Replace it with Ed25519; we described how to create a new key in the knowledge base of our hosting brand, aWh.

grep -r "ssh-dss" /home/*/.ssh/authorized_keys /root/.ssh/authorized_keys 2>/dev/null

Dracut, cgroup v1, APT 3

  • The initramfs is now generated by Dracut by default instead of initramfs-tools (the latter is still supported).
  • systemd no longer supports cgroup v1. If the machine has very old container images, or LXC containers running old systems that only work with cgroup v1, check them before you upgrade.
  • The apt-key command has been removed. Put the keys of external repositories in the /etc/apt/keyrings/ directory and refer to them with the signed-by option in the repository definition.
  • This is the last release in which systemd still runs old System V-style init scripts. If you have your own /etc/init.d/ scripts, now is a good time to replace them with systemd units.

Databases and application servers

MySQL comes as 8.4 LTS instead of 8.0. This is a bigger jump than it looks: 8.4 disables the old mysql_native_password authentication by default, and the default values of several settings have changed too. We collected the details in our article on MySQL 8.0 EOL. PHP 8.5 and PostgreSQL 18 are also major version changes; after the upgrade, PostgreSQL databases have to be moved to the new major version with the pg_upgradecluster command.

Hardware and cloud

  • amd64v3 package variants (builds optimised for newer x86 processors) can be selected with an APT setting; the cloud AMD64 images are already built with them.
  • Livepatch’s rebootless kernel updates are now available on Arm-based servers too.
  • In the release notes, Canonical lists a few older cloud instance types (for example older Google Cloud N1 and AWS generations) on which 26.04 is no longer supported. For cloud machines, check before you upgrade whether yours is on the list.

When should you upgrade from 24.04?

Standard support for 24.04 LTS lasts until 2029, so there is no need to rush. According to the release announcement, Canonical will only offer the upgrade automatically to 24.04 machines when 26.04.1 comes out, scheduled for 4 August 2026. By then the bug fixes of the first months will be included too.

Our recommendation:

  • You can install new servers on 26.04 right now, if your application supports it.
  • Upgrade existing production servers after 26.04.1 is released, and try it on a clone or test machine first.
  • You can’t go directly from 22.04 to 26.04: you have to upgrade to 24.04 first. Standard support for 22.04 ends in spring 2027, so it’s worth working through those machines this year.

We described what 24.04 brought at the time, and how the upgrade went, in our article on Ubuntu 24.04 LTS. The steps are similar now:

# 1. fresh backup or snapshot of the machine
# 2. full update of the current release
sudo apt update && sudo apt full-upgrade
sudo reboot

# 3. release upgrade (on 24.04 it is offered after 26.04.1 is released)
sudo do-release-upgrade

You can also run the release upgrade over SSH: in that case do-release-upgrade also opens a fallback SSH port in case the connection drops. It is safer, however, to start it in a screen or tmux session, or with console access.

What to check before upgrading

  1. Make a backup or snapshot, and test the restore.
  2. Check whether external repositories (PPAs, vendor repositories: Docker, PostgreSQL, Node.js) already provide packages for 26.04.
  3. Look for DSA keys and repository keys added with apt-key.
  4. Test your own scripts with rust-coreutils and sudo-rs.
  5. If MySQL runs on the machine, prepare for the switch to 8.4; with PostgreSQL, for the major version upgrade.
  6. Check that your cloud instance type is supported.
  7. After the upgrade, go through the logs (journalctl -p err -b) and the state of the services (systemctl --failed).

If you still have Ubuntu 20.04 running, it only gets security fixes with Ubuntu Pro, so move that machine to the front of the queue.

We also help with upgrading, operating and assessing Ubuntu servers; you can read more on our Infrastructure and operations page.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch