SSD Nodes Learn Hosting plans →
Guides Matt ConnorBy Matt Connor

Ubuntu 22.04 end of life: what to do

Ubuntu 22.04 standard support ends in May 2027. Check your exposure, then pick an exit: one hop to 24.04, two to 26.04, Ubuntu Pro, or a rebuild.

What Ubuntu 22.04 end of life means for your servers

Ubuntu 22.04 end of life starts in May 2027, when standard security maintenance for 22.04 LTS (long term support) ends. After that month, a 22.04 server without Ubuntu Pro stops getting new security fixes for the packages in the Main repository. The server does not shut down. It simply stops being patched.

There are four ways out. You can upgrade once to 24.04 LTS and stop there. You can upgrade twice and reach 26.04 LTS. You can attach Ubuntu Pro and keep 22.04 patched until May 2032. Or you can build a fresh server and move your services to it. This guide helps you pick one. It also covers the breakage around the date that people tend to miss, because the release upgrade itself is rarely the hard part.

Which Ubuntu 22.04 dates matter, and what does each one stop?

Canonical's release cycle page, read on 25 October 2026, lists these dates for 22.04 LTS. 22.04 came out in April 2022. The page gives months, not days.

  • May 2027: standard security maintenance ends. This is the date most people mean when they say "end of life".
  • May 2032: ESM (Expanded Security Maintenance) ends. ESM comes through Ubuntu Pro. The page's break/bug support column ends the same month.
  • May 2037: the Legacy add-on ends. Canonical sells it separately. It adds 5 more years after the 10-year ESM period, for 15 years of security maintenance in total.

The same page shows what each newer LTS buys you. 24.04 LTS gets standard security maintenance until May 2029, ESM until May 2034 and Legacy until May 2039. 26.04 LTS came out in April 2026. It gets standard maintenance until May 2031, ESM until May 2036 and Legacy until May 2041.

Read those dates as deadlines for patches, not for uptime. On the day standard maintenance ends, nothing on the server switches off. What stops is the flow of CVE (Common Vulnerabilities and Exposures) fixes from Canonical. Any new vulnerability found after that month stays open on your machine.

Main and Universe: what standard support never covered

The Ubuntu archive is split into repositories, and two of them matter here. Main is the set of packages Canonical chose as its focus when it launched Ubuntu. Universe holds all the other open source packages in Ubuntu.

Standard security maintenance is a 5-year commitment to CVE patches for packages in Main, and it needs no subscription. Canonical's ESM page describes two ESM streams, and both come through Ubuntu Pro:

  • esm-infra covers Main packages after the 5 years of standard maintenance end.
  • esm-apps covers all Universe packages for ten years from the LTS release.

In short, standard support covers Main, and Universe coverage comes with Ubuntu Pro. If your server runs packages from Universe, do not treat May 2027 as the day your exposure starts, because standard support was never what covered those packages. The ESM page also mentions a lower-cost "Ubuntu Pro (infra-only)" subscription for people who need only the esm-infra stream. That option leaves Universe out, so check what you run before you choose it.

How do I check my own exposure?

Run these on each 22.04 server. Do it before you pick an exit, because the answer changes which exit is cheapest.

cat /etc/os-release
sudo apt update
pro status
pro security-status
ubuntu-security-status

On a 22.04 machine, /etc/os-release should show VERSION_ID="22.04". Run sudo apt update before the other commands. The Ubuntu Pro client docs say the apt caches must be up to date for security-status to give accurate results.

pro status shows the status of each Ubuntu Pro service on the machine, so it tells you whether this server is attached to a subscription at all. pro security-status gives an overview of the installed packages, grouped by the repository they came from, with the security coverage that applies to each group. Look at how many packages it places in Universe or outside the Ubuntu archive.

ubuntu-security-status is a separate command. Run it and read what it reports for your machine. To see its options, run man ubuntu-security-status on the server itself, so you read the version you actually have.

The pro client has versions, and so do its online docs. Run pro --version and compare it with the version of the docs you are reading.

Next, list the software that did not come from Ubuntu, because the release upgrade handles it differently:

ls /etc/apt/sources.list.d/
grep -rl jammy /etc/apt/sources.list.d/
apt-cache policy
systemctl list-units --type=service --state=running

jammy is the codename of 22.04, so the grep shows every extra repository pinned to this release. apt-cache policy prints every repository apt knows about. The last command lists the services you will have to test after any change. Save all of this output somewhere off the server.

The four exits, and when each one fits

Exit 1: one hop to 24.04, then stop

This fits most servers. It is one release upgrade, and it moves your standard support date from May 2027 to May 2029. Ubuntu's upgrade guide says you can only upgrade from one LTS directly to the next sequential LTS. The release cycle page lists 24.04 LTS as the upgrade path for 22.04. So the next stop for a 22.04 server is always 24.04.

The same guide recommends do-release-upgrade on Server edition and cloud images. It also calls a backup to another location "extremely important" before you start. Take one. Then bring 22.04 fully up to date and start the upgrade:

sudo apt update && sudo apt full-upgrade
[ -f /var/run/reboot-required ] && sudo reboot
sudo do-release-upgrade

When it finishes and the server has rebooted, cat /etc/os-release should show VERSION_ID="24.04". If do-release-upgrade reports that no new release is found, read why do-release-upgrade finds no new release before you change any config.

Stop at 24.04 if your stack is tested there, or if your vendors certify 24.04 and not yet 26.04. You then have until May 2029 to plan the next move. That is a much calmer deadline.

Exit 2: two hops to 26.04

This fits when you want the longest runway from one project: standard support until May 2031. There is no shortcut. You cannot skip a release, so a 22.04 server reaches 26.04 by passing through 24.04. Each hop has its own breakage. The second hop also moves your language runtimes two releases away from what your code was tested on.

Ubuntu only offers an upgrade from one LTS to the next after the first point release of the new LTS. Ubuntu 26.04.1 LTS was announced on 27 August 2026. On 29 September 2026, Canonical announced that upgrades from 24.04 LTS to 26.04.1 LTS were enabled, and that server users can start one with do-release-upgrade. So both hops are open today.

The mechanics of each hop are in the full guide to upgrading Ubuntu 22.04 to 26.04, so they are not repeated here. Two pieces of advice matter for an end of life decision. Test your services on 24.04 before you start the second hop. And keep the -d flag off production servers: Canonical's upgrade guide says it is "not recommended for production environments." The flag does not only select a development release. Before a new LTS has its first point release, the guide says "users can force the upgrade via the -d flag" to that LTS, for example to evaluate it on a subset of machines. Both hops are open without it now, so a production server has no reason to use it. To see what 26.04.1 itself changed before you commit, read what changed in Ubuntu 26.04.1 and when to upgrade.

Exit 3: attach Ubuntu Pro to buy time

This fits when something keeps you on 22.04 for now. Examples: an application certified only on 22.04, a vendor repository with no 24.04 build yet, a team with no time this year, or a server you plan to retire before 2032. Ubuntu Pro gives a 22.04 server ESM until May 2032.

Pro is often described as a paid product only. It also has a free tier. As of 25 October 2026, ubuntu.com/pro says: "Ubuntu Pro is and always will be free for personal use on up to 5 physical machines, or 50 machines for official Ubuntu Community members." Note the words "physical machines". The page does not say how a VPS counts against that limit, so read the subscription terms before you rely on the free tier for a cloud server. For business use, the same page offers a 30-day trial for enterprises. It shows no prices, so ask Canonical for a quote rather than trusting a figure from a forum.

Attaching takes one command:

sudo pro attach
pro status

sudo pro attach prints a link, https://ubuntu.com/pro/attach, and a code. Open the link, sign in, enter the code, and choose a subscription. The Ubuntu Pro client docs say the free personal token is selected by default. Afterwards, pro status should list the services the subscription enabled. For the full picture of services, tokens and what Pro changes on a machine, see Ubuntu Pro on a server, explained.

Be clear about what Pro does not do. It keeps 22.04 patched. It does not give you newer software. ESM covers Main and Universe, so PPAs and third-party repositories get nothing from it. And the upgrade you postponed still waits for you, only later and with more releases in between.

Exit 4: rebuild fresh and migrate

This fits a server that has collected years of hand edits, or many PPAs that nobody remembers adding. It also fits when you want 26.04 without two in-place hops. You create a new server on 24.04 or 26.04, install your stack there, copy the data, test it, and switch DNS. The old server stays up until the new one has proved itself. That gives you a rollback that an in-place upgrade does not.

A rebuild is easier to repeat when you write it down as code. A first Ansible playbook for a VPS turns the next rebuild into a single command. For the trade-offs in detail, read whether to upgrade in place or reinstall Ubuntu Server.

Which exit should I pick?

  • One server, standard stack, packages mostly from Main: one hop to 24.04.
  • You want the longest support from a single project, and you can test between hops: two hops to 26.04, or a rebuild straight onto 26.04.
  • A blocker keeps you on 22.04, and the machine qualifies for a Pro subscription: attach Pro, then put a date in the calendar for the real move.
  • Heavy PPA use or an unknown history: rebuild and migrate.

The breakage around the date that people miss

Third-party repositories and PPAs

A PPA (Personal Package Archive) or a vendor repository publishes packages for each Ubuntu codename separately. Ubuntu's upgrade guide says third-party repositories and PPAs are disabled during the release upgrade. Turning them back on is a manual step. It only works if the repository publishes packages for the new codename: noble for 24.04, or resolute for 26.04. Before you upgrade, check each repository's own docs for that, using the list you saved from /etc/apt/sources.list.d/.

Staying on 22.04 does not protect you from this. A repository maintainer can stop building for jammy on their own schedule, which has nothing to do with Canonical's dates. If they delete the jammy suite, apt update fails for that source with an error saying the repository does not have a Release file. If they only stop publishing, nothing warns you. The package just stays at the last version you installed.

Language runtimes tied to 22.04 packages

The python3, php, nodejs or ruby you installed with apt is the version 22.04 shipped. A release upgrade replaces each one with the version from the new release. Code that was only tested on the old version can break. A Python virtual environment built on the old interpreter may need to be rebuilt. Record the versions before you start:

python3 --version
php --version
node --version
ruby --version

Some of these may print "command not found". That is fine. It means that runtime is not installed on this server. Then read each runtime's docs and your application's docs for the versions they support on 24.04 or 26.04. A runtime you installed from a vendor repository belongs in the PPA section above, because it depends on that vendor publishing for the new codename.

Container images built on 22.04

Upgrading the host does not touch your containers. A container runs the userland of the image it was built from. So a container built FROM ubuntu:22.04 is a 22.04 system inside, with the same dates, even on a 26.04 host. It keeps running after May 2027, and nothing inside it tells you that it has stopped getting fixes.

Find them on each Docker host:

docker ps
docker image ls
docker run --rm --entrypoint cat your-image:tag /etc/os-release
grep -rnE 'ubuntu:22.04|jammy' --include='Dockerfile*' .

The third command prints the release inside an image, as long as the image contains cat. The last one searches your own Dockerfiles. Move each base image to a 24.04 or 26.04 tag, rebuild, and test. The ESM page says nothing about container images, so check ubuntu.com/pro before you plan to cover images with Pro. If your stack runs on Compose, backing up and upgrading a Docker Compose stack covers a safe way to roll the new images out.

Your provider's 22.04 image

Your recovery plan may be "reinstall 22.04 from the provider image and restore the backup". If so, check today that your provider still offers that image. Each provider decides this for itself, and an image you rely on can be removed before you need it. The same check applies before a rebuild: confirm that the 24.04 or 26.04 image you want is there.

How this compares with earlier end of life dates

The pattern is the same for every LTS, and Debian works in a similar way. If you went through the 20.04 cutoff, the Ubuntu 20.04 end of life upgrade path follows the same logic one release earlier. A mixed fleet with Debian 11 servers faces the same choice in different words, covered in the Debian 11 end of life upgrade path. Whichever exit you take, finish with a scan. Checking your server for known CVEs confirms that the server you end up with is actually patched.

FAQ

Does my Ubuntu 22.04 server stop working in May 2027?

No. According to ubuntu.com/about/release-cycle, standard security maintenance for 22.04 ends in May 2027. The server keeps running. What stops is new security fixes for Main packages, unless the machine is attached to Ubuntu Pro, which extends ESM to May 2032. Any vulnerability found after the cutoff stays open on a server without Pro.

Is Ubuntu Pro free for a server?

As of 25 October 2026, ubuntu.com/pro says Pro is free for personal use on up to 5 physical machines, or 50 machines for official Ubuntu Community members. The page says "physical machines" and does not say how a VPS counts, so read the terms before you rely on it for a cloud server. For business use, the page offers a 30-day trial for enterprises and shows no prices.

Can I upgrade straight from Ubuntu 22.04 to 26.04?

No. Ubuntu only supports upgrading from one LTS directly to the next sequential LTS, and you cannot skip releases. A 22.04 server reaches 26.04 by upgrading to 24.04 first, then to 26.04. If you want 26.04 without two in-place upgrades, build a new 26.04 server and migrate your data to it.

How do I see which of my packages lose security updates?

Run sudo apt update first. Then run pro security-status, which groups your installed packages by repository and shows the coverage for each group. ubuntu-security-status gives a second view, and man ubuntu-security-status explains its options. Pay attention to Universe packages: standard support covers Main, and Universe coverage comes with Ubuntu Pro.

Do Docker containers on a 22.04 host share its end of life?

A container follows its own base image, not the host. A container built from ubuntu:22.04 is a 22.04 system with the same dates, even on a 26.04 host. A container built from a different base does not follow the Ubuntu dates at all. Check an image with docker run --rm --entrypoint cat your-image:tag /etc/os-release, then move its base to a 24.04 or 26.04 tag and rebuild.

Was this article useful?