From Fedora Project Wiki
< Changes
mNo edit summary |
mNo edit summary |
||
| Line 86: | Line 86: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: Gather feedback, use cases for the Fedora base container image. | ||
Remove packages from the container image. | |||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: Possibly fix/update their dependency requirements. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Other developers: Possibly fix/update their dependency requirements in packages and container. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 96: | Line 97: | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
* Policies and guidelines: TBD, but most probably not needed. | * Policies and guidelines: TBD, but most probably not needed.<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
Revision as of 12:54, 30 October 2020
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.
Guidance
For details on how to fill out this form, see the documentation.
For details on how to fill out this form, see the documentation.
Fedora Base Container Image Minimization
Summary
Reduction in size of the Fedora Base container image by dropping packages that are not needed for the core function of the base image. Those base functionalities will be gathered and defined in the process.
Owner
- Name: Clement Verna Jakub Čajka
Current status
- Targeted release: Fedora 34
- Last updated: 2020-10-30
- 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>
Feedback
Please provide your use and use cases in the Container-SIG issue or on the Fedora devel ML.
Benefit to Fedora
Reduced size of the base container image would make Fedora more friendly for cloud container use while keeping all the Fedora features. Reduction of the packages that are part of image will also help to find and fix implicit dependencies in containers and packages.
Scope
- Proposal owners: Gather feedback, use cases for the Fedora base container image.
Remove packages from the container image.
- Other developers: Possibly fix/update their dependency requirements in packages and container.
- Release engineering: TBD #Releng issue number (a check of an impact with Release Engineering is needed)
- Policies and guidelines: TBD, but most probably not needed.
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
There should be no impact, breakage.
How To Test
N/A (not a System Wide Change)
User Experience
Dependencies
N/A (not a System Wide Change)
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
- Blocks product? product
Documentation
N/A (not a System Wide Change)