mNo edit summary |
mNo edit summary |
||
Line 56: | Line 56: | ||
== Benefit to Fedora == | == 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. | |||
<!-- 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? | ||
Revision as of 12:52, 30 October 2020
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:
- Other developers: Possibly fix/update their dependency requirements.
- 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. (not a System Wide Change)
- 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)