Changes/Podman5

Podman 5

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Ship Podman 5 in Fedora 40.

Owner

• Name: Lokesh Mandvekar, Mohan Boddu

Current status

• Targeted release: Fedora Linux 40
• Last updated: 2023-12-12
• Announced
• Discussion thread
• FESCo issue: <will be assigned by the Wrangler>
• Tracker bug: <will be assigned by the Wrangler>
• Release notes tracker: <will be assigned by the Wrangler>

Benefit to Fedora

Podman 5 will:

• No longer support cgroups v1
• Deprecate CNI plugins
• Deprecate Boltdb
• Have passt as the default rootless network service instead of slirp4netns
• Support stable --format Go template structs
• Isolate podman bindings leading to improved usability
• Allow better handling of containers.conf

Scope

• Proposal owners:

• Other developers:

• Release engineering: #Releng issue number

• Policies and guidelines: N/A (not needed for this Change)

• Trademark approval: N/A (not needed for this Change)

• Alignment with Community Initiatives:

Upgrade/compatibility impact

Podman 5 will come with breaking changes affecting upgradability:

• CGroups v1 environments will be required to switch to CGroups v2
• CNI plugin environemnts will need to switch to netavark
• Changes in --format Go template structs

How To Test

Probably best handled in a Podman Test Day aligned with Fedora 40 Test Days.

• Install Fedora 40
• Install Podman 5
• Run test cases / suite (TBD)

User Experience

Podman 5 will provide better usability of Podman bindings, easier to maintain containers.conf and other configuration files along with database performance improvements and CLI enhancements.

Dependencies

Projects / Packages likely to be affected:

• Cockpit
• CoreOS
• Toolbox
• Silverblue / Kinoite
• Podman Desktop

Contingency Plan

• Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
• Contingency deadline: N/A (not a System Wide Change)
• Blocks release? N/A (not a System Wide Change), Yes/No

Documentation

N/A (not a System Wide Change)