From Fedora Project Wiki
< Changes
Line 144: | Line 144: | ||
== User Experience == | == 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. | |||
<!-- If this change proposal is noticeable by users, how will their experiences change as a result? | <!-- If this change proposal is noticeable by users, how will their experiences change as a result? | ||
Revision as of 14:19, 5 December 2023
Podman 5
Summary
Ship Podman 5 in Fedora 40.
Owner
- Name: Lokesh Mandvekar, Mohan Boddu
Current status
- Targeted release: Fedora Linux 40
- Last updated: 2023-12-05
- [<will be assigned by the Wrangler> devel 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>
Detailed Description
Feedback
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
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 affected:
- Cockpit
- CoreOS
- Toolbox
- Silverblue / Kinoite
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)