Install Podman on Debian: APT, Versions & Rootless Setup

On Debian, Podman installs from the main archive with two commands. The catch is which major version your release ships — Debian 12 still carries Podman 4.3.x while Debian 13 ships 5.4.x. Check that before copying flags from a tutorial written for Fedora or upstream docs.

Quick install Podman on Debian

Refresh package indexes first:

sudo apt update

Install Podman from the main archive:

sudo apt install podman

Confirm the client version immediately:

podman --version

Sample output on Debian 13:

podman version 5.4.2

If that version line prints, the package and its runtime dependencies are on the PATH. Continue with podman info and the hello container below.

Podman versions on Debian 12 and 13

Debian pins one Podman branch per stable release. The exact Debian revision changes with security updates, but the major.minor is what matters for feature compatibility.

Why this split matters:

• Debian 12's Podman 4.3 branch predates several newer Quadlet capabilities and 5.x CLI helpers.
• Debian 13's 5.4 branch supports substantially more current functionality, but still trails the latest upstream 5.8 minor.

Before following newer 5.6 or 5.8 examples, compare your podman --version output to the feature matrix on Install Podman on RHEL.

Ask APT what your host would install:

apt-cache policy podman

Sample output on Debian 12:

podman:
  Installed: (none)
  Candidate: 4.3.1+ds1-8+deb12u1+b3
  Version table:
     4.3.1+ds1-8+deb12u1+b3 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages

The Candidate line is the version apt install podman selects from enabled repositories.

Install Podman

Run the install transaction on your Debian host:

sudo apt install podman

APT pulls the runtime stack automatically on a normal install:

• conmon — per-container supervisor
• crun or runc — OCI runtime (Debian resolves one of these)
• netavark — networking on Trixie; Bookworm may differ
• fuse-overlayfs — rootless-friendly storage
• uidmap — subordinate ID tools for rootless mode (recommended package; installed by default unless you pass --no-install-recommends)

You do not need to install those packages manually on a normal Debian install.

Verify the Podman installation

Check the client version:

podman --version

Inspect the runtime stack with podman info:

podman info

Read these fields in the output (structure varies by Debian release):

cgroupVersion: v2
  networkBackend: netavark
  ociRuntime:
    name: crun
  graphDriverName: overlay

If podman info fails after installation, read the reported error first. Check runtime/configuration and package state before reinstalling Podman — see Podman troubleshooting for common causes.

Verify rootless Podman on Debian

Rootless Podman runs as your login user without sudo. A normal apt install podman also installs the recommended rootless helper packages such as uidmap on supported Debian releases. You still need subordinate ranges for that user.

Verify uidmap is present if you used --no-install-recommends or rootless setup fails:

dpkg -l uidmap

Check UID delegation:

grep "^$(id -un):" /etc/subuid

Check GID delegation:

grep "^$(id -un):" /etc/subgid

As that user (not root), confirm Podman reports rootless mode:

podman info --format 'rootless={{.Host.Security.Rootless}}'

Sample output:

rootless=true

Missing or unsuitable subordinate UID/GID mappings are a common cause of rootless container failures, especially when images require multiple mapped IDs. When ranges are missing or pulls fail with user-namespace errors, follow Rootless Podman — this install guide only confirms the smoke test.

Run a test container

Pull and run the hello image to exercise registry access, storage, the OCI runtime, and conmon:

podman run --rm quay.io/podman/hello

Sample output:

!... Hello Podman World ...!

The greeting confirms image pull, overlay storage, the OCI runtime, and cleanup with --rm.

Next lesson: Run containers with podman run for detach mode, ports, and environment variables.

Update Podman on Debian

Use the normal APT upgrade path:

sudo apt update

Upgrade the package when a security or bugfix revision appears:

sudo apt upgrade podman

Re-run podman --version after upgrades. Debian rarely jumps major versions on an existing stable release.

Uninstall Podman from Debian

Remove the package when you no longer need containers on the host:

sudo apt remove podman

Drop configuration files as well when you want a cleaner removal:

sudo apt purge podman

Removing the package does not delete images, containers, or volumes. Rootful storage often remains under /var/lib/containers; rootless users keep ~/.local/share/containers/. Delete those directories only when you intentionally want a full wipe.

Common installation problems on Debian

References

• Podman installation documentation
• Debian podman package — bookworm
• Debian podman package — trixie

Summary

Installing Podman on Debian is sudo apt update followed by sudo apt install podman. Debian 12 Bookworm ships Podman 4.3.x; Debian 13 Trixie ships 5.4.x in current archives. Run apt-cache policy podman on your host and compare the candidate to tutorials before copying newer Quadlet or CLI examples.

podman info shows the cgroup version, storage driver, and network backend active on your host. A rootless smoke test and the hello image prove user-namespace mappings and runtime integration. For Ubuntu paths, see Install Podman on Ubuntu; for Quadlet feature gates, see Install Podman on RHEL.