From Fedora Project Wiki
< Changes
Line 122: | Line 122: | ||
== How To Test == | == 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) | |||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | ||
Line 137: | Line 142: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== User Experience == | == User Experience == |
Revision as of 14:15, 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
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)