Beyond the Default: Upgrading Podman via the Resolute Repository on Ubuntu

While Ubuntu’s official repositories provide a stable version of Podman, they often lag several versions behind the upstream releases from the Podman team. For developers requiring the latest features in rootless networking, Quadlet support, or improved Docker-compose compatibility, the default apt packages may be insufficient. The Resolute repository (maintained as part of the broader community efforts to provide up-to-date container tools) serves as a vital bridge. By adding this repository to your system, you can access cutting-edge builds of the Podman engine and its dependencies (like conmon and skopeo) without waiting for the next Ubuntu LTS point release.

Table of Content

• Purpose of Using External Repositories
• Why Upgrade Your Podman Version?
• Step-by-Step Installation Guide
• Best Results: Post-Upgrade Verification
• FAQ
• Disclaimer

Purpose

The primary purpose of utilizing the Resolute repository is Version Parity. Ubuntu's "stable" philosophy means that if you install Podman today on a 22.04 machine, you might get version 3.4.x, while the current upstream is at 5.x. This discrepancy can lead to:

• Incompatible Container Images: Newer images may require storage driver features not present in older Podman versions.
• Security Vulnerabilities: Older versions may lack the latest patches for rootless container escapes.
• Missing Tools: Essential features like podman machine for Mac/Windows-like workflows are often broken or missing in older Linux builds.

Use Case

Upgrading via Resolute is recommended for:

• CI/CD Pipelines: Ensuring that your local build environment matches the latest container runtime specifications used in production.
• Docker Migration: Users moving from Docker to Podman who need the podman-docker alias to behave identically to modern Docker CLI versions.
• Advanced Networking: Utilizing netavark and aardvark-dns for complex bridge networking in rootless mode.

Step-by-Step

1. Remove the Existing Podman Installation

To avoid dependency conflicts between the Ubuntu archive and the Resolute repo, it is often cleaner to start fresh.

• Run: sudo apt-get purge podman -y
• Run: sudo apt-get autoremove -y

2. Add the Resolute GPG Key and Repository

You must authorize your system to trust the packages from the Resolute source.

1. Import the GPG key: curl -fsSL https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_$(lsb_release -rs)/Release.key | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/resolute-podman.gpg
2. Add the repository line: echo "deb [signed-by=/etc/apt/trusted.gpg.d/resolute-podman.gpg] https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/stable/xUbuntu_$(lsb_release -rs)/ /" | sudo tee /etc/apt/sources.list.d/resolute-podman.list

3. Update and Install

Now that the source is added, trigger the package manager to fetch the latest version.

• Run: sudo apt-get update
• Run: sudo apt-get install podman -y

4. Configure Rootless Access

Ensure your user has the necessary subuid/subgid mapping for the new version.

• Verify mapping: cat /etc/subuid
• If empty, populate it: sudo usermod --add-subuids 100000-165535 --add-subgids 100000-165535 $USER

Best Results

FAQ

Will this repository break my system updates?

Because Resolute specifically targets container tools (Kubic/Libcontainers), it rarely conflicts with core Ubuntu system libraries. However, it is a third-party source, so you should pin its priority if you want to avoid accidental upgrades of other shared libraries.

Can I revert to the Ubuntu version?

Yes. Simply remove the file in /etc/apt/sources.list.d/resolute-podman.list, run sudo apt update, and reinstall podman. APT will default back to the official Ubuntu archives.

Does this work on WSL2?

Yes. In fact, using the latest Podman from Resolute is the preferred way to run Podman in WSL2 (Ubuntu), as it includes better support for the specialized networking drivers used by Windows.

Disclaimer

The Resolute repository is a community-driven project. While it is widely used and generally considered stable, it does not carry the official support of Canonical or Red Hat. Always backup your container volumes and configurations before performing a major version jump. This tutorial is valid for Ubuntu 22.04 and 24.04 as of March 2026.

Tags: Podman, Ubuntu, Containers, DevOps