(adding release notes tracker) |
|||
(12 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
= Podman 5 <!-- The name of your change proposal --> = | = Podman 5 <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
Line 28: | Line 18: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF40]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Line 46: | Line 36: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* [ | * [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/ES4M2ZTGASS2P3G2EM57LNXIP2FFWIHD/ Announced] | ||
* FESCo issue: | *[https://discussion.fedoraproject.org/t/f40-change-proposal-podman-5-self-contained/98914 Discussion thread] | ||
* Tracker bug: | * FESCo issue: [https://pagure.io/fesco/issue/3126 #3126] | ||
* Release notes tracker: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2258071 #2258071] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/1096 #1096] | |||
== Detailed Description == | == Detailed Description == | ||
Line 58: | Line 49: | ||
== Benefit to Fedora == | == 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 | |||
<!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | <!-- What is the benefit to the distribution? Will the software we generate be improved? How will the process of creating Fedora releases be improved? | ||
Line 107: | Line 107: | ||
== Upgrade/compatibility impact == | == 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 | |||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== 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 129: | Line 140: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== 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? | ||
Line 143: | Line 156: | ||
== Dependencies == | == Dependencies == | ||
Projects / Packages likely to be affected: | |||
* Cockpit | |||
* CoreOS | |||
* Toolbox | |||
* Silverblue / Kinoite | |||
* Podman Desktop | |||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== Contingency Plan == | == Contingency Plan == |
Latest revision as of 20:37, 28 February 2024
Podman 5
Summary
Ship Podman 5 in Fedora 40.
Owner
- Name: Lokesh Mandvekar, Mohan Boddu
Current status
- Targeted release: Fedora Linux 40
- Last updated: 2024-02-28
- Announced
- Discussion thread
- FESCo issue: #3126
- Tracker bug: #2258071
- Release notes tracker: #1096
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
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)