How to install Podman on Ubuntu 24.04 step by step

Podman can usually be installed on Ubuntu 24.04 directly from the official package repos­i­to­ries using just a few commands. This makes setting up Podman on Ubuntu par­tic­u­lar­ly straight­for­ward, even for beginners.

Step 1: Check the pre­req­ui­sites for in­stal­la­tion

Before beginning the in­stal­la­tion, make sure Ubuntu 24.04 LTS is installed and con­fig­ured on your system. You will also need terminal access and a user account with sudo priv­i­leges to install and update system packages. An active internet con­nec­tion is required to download the Docker al­ter­na­tive Podman and its de­pen­den­cies from the Ubuntu package repos­i­to­ries.

For initial tests and smaller container projects, a VPS is usually suf­fi­cient for running Podman on Ubuntu. A dedicated server may be the better option if you plan to run several con­tain­ers at the same time, use resource-intensive ap­pli­ca­tions or create a pre­dictable en­vi­ron­ment for pro­duc­tion workloads.

Podman itself has rel­a­tive­ly modest system re­quire­ments. However, your server should have enough free storage space, at least 2 GB of RAM and a properly main­tained Ubuntu in­stal­la­tion.

Step 2: Update the package lists

In­stalling Podman on Ubuntu only takes a few steps. Start by updating your system’s package lists so Ubuntu can retrieve the latest available package in­for­ma­tion from the con­fig­ured repos­i­to­ries.

sudo apt update

You can then op­tion­al­ly update all installed packages to their latest versions:

sudo apt upgrade -y

This step is par­tic­u­lar­ly useful on freshly set-up systems, as it updates existing packages and libraries. This reduces the like­li­hood of un­nec­es­sary version conflicts occurring later during the in­stal­la­tion.

Step 3: Enable the Universe repos­i­to­ry

On Ubuntu 24.04, software sources are typically con­fig­ured using files in /etc/apt/sources.list.d/. Podman is available through the Universe repos­i­to­ry, which may not be enabled in some in­stal­la­tions. If necessary, activate it with the following command:

sudo add-apt-repository universe
sudo apt update

On many systems, Universe is already active. In that case, the command does no harm; it simply confirms the existing con­fig­u­ra­tion.

Step 4: Install Podman

You can now install Podman directly using the package manager:

sudo apt install podman -y

Ubuntu 24.04 includes Podman in its standard package repos­i­to­ries, so there is no need to add a third-party source or use a separate in­stal­la­tion script. The APT package manager downloads Podman and its required de­pen­den­cies au­to­mat­i­cal­ly and installs them on your system.

Step 5: Verify the in­stal­la­tion

After in­stal­la­tion, verify that Podman has been set up correctly by checking the installed version:

podman --version

If the in­stal­la­tion was suc­cess­ful, the output will display the installed Podman version.

Close

You can also use the following command to display more detailed in­for­ma­tion about the Podman en­vi­ron­ment:

podman info

This command shows, among other things, in­for­ma­tion about the host en­vi­ron­ment, storage and runtime con­fig­u­ra­tions, as well as the container reg­istries in use. Es­pe­cial­ly if problems occur later on, podman info is often one of the first useful di­ag­nos­tic commands.

Close

Step 6: Verify the in­stal­la­tion with a test container

The simplest way to check that Podman is not only installed but also working correctly is to run a small test container. You can use the hello-world container for this purpose and start it with the following command:

podman run --rm hello-world

If the image is not already available locally, Podman downloads it au­to­mat­i­cal­ly from a container registry such as Docker Hub before starting the container. The --rm option removes the test container as soon as it finishes running. If the test is suc­cess­ful, a short message confirms that Podman can run con­tain­ers correctly.

Close

The first run may take a little longer if Podman needs to download the image from a registry. This is normal. Once the image is stored locally, sub­se­quent runs are usually much faster.