How To Upgrade to Ubuntu 22.04 Jammy Jellyfish

Published on April 25, 2022
Default avatar

By Alex Garnett

Senior DevOps Technical Writer

How To Upgrade to Ubuntu 22.04 Jammy Jellyfish
Not using Ubuntu 22.04?Choose a different version or distribution.
Ubuntu 22.04


The Ubuntu operating system’s latest Long Term Support (LTS) release, Ubuntu 22.04 (Jammy Jellyfish), was released on April 21, 2022. This guide will explain how to upgrade an Ubuntu system of version 20.04 or later to Ubuntu 22.04.

Warning: As with almost any upgrade between major releases of an operating system, this process carries an inherent risk of failure, data loss, or broken software configuration. Comprehensive backups and extensive testing are strongly advised.

To avoid these problems, we recommend migrating to a fresh Ubuntu 22.04 server rather than upgrading in-place. You may still need to review differences in software configuration when upgrading, but the core system will likely have greater stability. You can follow our series on how to migrate to a new Linux server to learn how to migrate between servers.


This guide assumes that you have an Ubuntu 20.04 or later system configured with a sudo-enabled non-root user.

Potential Pitfalls

Although many systems can be upgraded in place without incident, it is often safer and more predictable to migrate to a major new release by installing the distribution from scratch, configuring services with careful testing along the way, and migrating application or user data as a separate step.

You should never upgrade a production system without first testing all of your deployed software and services against the upgrade in a staging environment. Keep in mind that libraries, languages, and system services may have changed substantially. Before upgrading, consider reading the Jammy Jellyfish Release Notes.

Step 1 – Backing Up Your System

Before attempting a major upgrade on any system, you should make sure you won’t lose data if the upgrade goes awry. The best way to accomplish this is to make a backup of your entire filesystem. Failing that, ensure that you have copies of user home directories, any custom configuration files, and data stored by services such as relational databases.

On a DigitalOcean Droplet, one approach is to power down the system and take a snapshot (powering down ensures that the filesystem will be more consistent). See How to Create Snapshots of Droplets for more details on the snapshot process. After you have verified that the Ubuntu update was successful, you can delete the snapshot so that you will no longer be charged for its storage.

For backup methods which will work on most Ubuntu systems, see How To Choose an Effective Backup Strategy for your VPS.

Step 2 – Updating Currently Installed Packages

Before beginning the release upgrade, it’s safest to update to the latest versions of all packages for the current release. Begin by updating the package list:

  1. sudo apt update

Next, upgrade installed packages to their latest available versions:

  1. sudo apt upgrade

You will be shown a list of upgrades, and prompted to continue. Press y to confirm and press Enter.

This process may take some time. Once it finishes, use the dist-upgrade command with apt-get, which will perform any additional upgrades that involve changing dependencies, adding or removing new packages as necessary. This will handle a set of upgrades which may have been held back by the previous apt upgrade step:

  1. sudo apt dist-upgrade

Again, answer y when prompted to continue, and wait for upgrades to finish.

Now that you have an up-to-date installation of Ubuntu, you can use do-release-upgrade to upgrade to the 22.04 release.

Step 3 – Upgrading with Ubuntu’s do-release-upgrade Tool

Traditionally, Ubuntu releases have been upgradeable by changing Apt’s /etc/apt/sources.list – which specifies package repositories – and using apt-get dist-upgrade to perform the upgrade itself. Though this process is still likely to work, Ubuntu provides a tool called do-release-upgrade to make the upgrade safer and easier.

do-release-upgrade handles checking for a new release, updating sources.list, and a range of other tasks, and is the officially recommended upgrade path for server upgrades which must be performed over a remote connection.

Start by running do-release-upgrade with no options:

  1. sudo do-release-upgrade

If the new Ubuntu version has not been officially released yet, you may get the following output:

Checking for a new Ubuntu release No new release found

Note that on Ubuntu Server, the new LTS release isn’t made available to do-release-upgrade until its first point release, in this case 22.04.1. This usually comes a few months after the initial release date.

If you don’t see an available release, add the -d option to upgrade to the development release:

  1. sudo do-release-upgrade -d

If you’re connected to your system over SSH, you’ll be asked whether you wish to continue. For virtual machines or managed servers you should keep in mind that losing SSH connectivity is a risk, particularly if you don’t have another means of remotely connecting to the system’s console (such as a web-based console feature, for example).

For other systems under your control, remember that it’s safest to perform major operating system upgrades only when you have direct physical access to the machine.

At the prompt, type y and press Enter to continue:

Reading cache Checking package manager Continue running under SSH? This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover. If you continue, an additional ssh daemon will be started at port '1022'. Do you want to continue? Continue [yN]

Next, you’ll be informed that do-release-upgrade is starting a new instance of sshd on port 1022:

Starting additional sshd To make recovery in case of failure easier, an additional sshd will be started on port '1022'. If anything goes wrong with the running ssh you can still connect to the additional one. If you run a firewall, you may need to temporarily open this port. As this is potentially dangerous it's not done automatically. You can open the port with e.g.: 'iptables -I INPUT -p tcp --dport 1022 -j ACCEPT' To continue please press [ENTER]

Press Enter. Next, you may be warned that a mirror entry was not found. On DigitalOcean systems, it is safe to ignore this warning and proceed with the upgrade, since a local mirror for 22.04 is in fact available. Enter y:

Updating repository information No valid mirror found While scanning your repository information no mirror entry for the upgrade was found. This can happen if you run an internal mirror or if the mirror information is out of date. Do you want to rewrite your 'sources.list' file anyway? If you choose 'Yes' here it will update all 'focal' to 'jammy' entries. If you select 'No' the upgrade will cancel. Continue [yN]

Once the new package lists have been downloaded and changes calculated, you’ll be asked if you want to start the upgrade. Again, enter y to continue:

Do you want to start the upgrade? 4 packages are going to be removed. 107 new packages are going to be installed. 554 packages are going to be upgraded. You have to download a total of 547 M. This download will take about 1 minute with a 40Mbit connection and about 14 minutes with a 5Mbit connection. Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be canceled. Continue [yN] Details [d]

You may receive another warning about not being able to disable a lock screen:

Unable to disable lock screen It is highly recommended that the lock screen be disabled during the upgrade to prevent later issues. Please ensure your screen lock is disabled before continuing.

If you are connecting to a Ubuntu server, rather than a desktop, you can ignore this warning by pressing Enter.

New packages will now be retrieved, unpacked, and installed. Even if your system is on a fast connection, this will take a while.

During the installation, you may be presented with interactive dialogs for various questions. For example, you may be asked if you want to automatically restart services when required:

Service Restart Dialog

In this case, it is safe to answer Yes. In other cases, you may be asked if you wish to replace a configuration file that you have modified. This is often a judgment call, and is likely to require knowledge about specific software that is outside the scope of this tutorial.

Once new packages have finished installing, you’ll be asked whether you’re ready to remove obsolete packages. On a stock system with no custom configuration, it should be safe to enter y here. On a system you have modified heavily, you may wish to enter d and inspect the list of packages to be removed, in case it includes anything you’ll need to reinstall later.

Remove obsolete packages? 53 packages are going to be removed. Continue [yN] Details [d]

Finally, assuming all has gone well, you’ll be informed that the upgrade is complete and a restart is required. Enter y to continue:

System upgrade is complete. Restart required To finish the upgrade, a restart is required. If you select 'y' the system will be restarted. Continue [yN]

On an SSH session, you’ll likely see something like the following:

Connection to closed by remote host. Connection to closed.

You may need to press a key here to exit to your local prompt, since your SSH session will have terminated on the server end.

Wait a moment for your server to reboot, then reconnect. On login, you should be greeted by a message confirming that you’re now on Focal Fossa :

Welcome to Ubuntu 22.04 LTS (GNU/Linux 5.15.0-25-generic x86_64)


You should now have a working Ubuntu 22.04 installation. From here, you likely need to investigate necessary configuration changes to services and deployed applications.

You can find more 22.04 tutorials and questions on our Ubuntu 22.04 Tutorials tag page.

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about us

About the authors
Default avatar

Senior DevOps Technical Writer

Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

0 glitches. Then again I have only 1 Docker container to worry about.

Thanks for the tutorial.

After doing to upgrade and fixing the network issues as @wuijin1004 described, and I think that the cloud-init service is not working properly. The 50-cloud-init.yaml file only contains the mac address, and quite possibly won’t reflect any future changes by the cloud provider.

When I upgraded my Droplet from Ubuntu 20.04 to 22.04, I get the following errors:

Errors were encountered while processing:
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the automatically opened web browser.

What would you like to do? Your options are:
S: Send report (434.0 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
Please choose (S/V/K/I/C): c

Could not install the upgrades

The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a).

Setting up usbmuxd (1.1.1-2build2) ...
usbmuxd.service is a disabled or a static unit, not starting it.

Upgrade complete

The upgrade has completed but there were errors during the upgrade process.

Please advise on how I can fix this issue.

I follow this tutorial and the upgrade works fine until the server restarts. Then I cannot SSH into the server again. I get in using the recovery console and the server has no IP address and cannot ping anything except local host. I can restore the droplet from a backup and try the process again, but the result is the same. Why does the droplet lose its IP address after upgrading to 22.04?

do-release-upgrade does not work for me without RELEASE_UPGRADER_ALLOW_THIRD_PARTY=1

I had issues in Step 2 first command of “sudo apt update”

Going from 21.10 (Impish) to 22.04

This link provided the answer

See https://help.ubuntu.com/community/EOLUpgrades#Upgrading

I get the Please install all available updates for your release before upgrading. when trying to upgrade. I’ve already done apt update/upgrade/dist-upgrade. Any ideas for what could be the issue?

For me, the first step (sudo apt update) already fails. I get the following feedback:

Ign:1 http://archive.ubuntu.com/ubuntu groovy InRelease
Hit:2 http://deb.playonlinux.com trusty InRelease                                                                      
Ign:3 http://mirrors.digitalocean.com/ubuntu groovy InRelease                                                          
Err:4 http://archive.ubuntu.com/ubuntu groovy Release                                                                  
  404  Not Found [IP: 80]
Get:5 http://download.opensuse.org/repositories/Ubuntu:/debbuild/Ubuntu_20.04  InRelease [1210 B]                      
Ign:6 http://mirrors.digitalocean.com/ubuntu groovy-updates InRelease                                                  
Ign:7 http://mirrors.digitalocean.com/ubuntu groovy-backports InRelease    
Err:8 http://mirrors.digitalocean.com/ubuntu groovy Release                
  404  Not Found [IP: 80]
Err:9 http://mirrors.digitalocean.com/ubuntu groovy-updates Release
  404  Not Found [IP: 80]
Err:10 http://mirrors.digitalocean.com/ubuntu groovy-backports Release
  404  Not Found [IP: 80]
Ign:11 http://security.ubuntu.com/ubuntu groovy-security InRelease
Err:12 http://security.ubuntu.com/ubuntu groovy-security Release
  404  Not Found [IP: 80]
Reading package lists... Done
E: The repository 'http://archive.ubuntu.com/ubuntu groovy Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://mirrors.digitalocean.com/ubuntu groovy Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://mirrors.digitalocean.com/ubuntu groovy-updates Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://mirrors.digitalocean.com/ubuntu groovy-backports Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.ubuntu.com/ubuntu groovy-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I’m on Ubuntu 20.10.

Please fix the Ubuntu version in the first sentence. It should be “Ubuntu 22.04 (Jammy Jellyfish), was released on April 21, 2022”

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Join the Tech Talk
Success! Thank you! Please check your email for further details.

Please complete your information!

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel