Squeezing Fedora into IoT & clouds (Minimization)
summary
Fedora Minimization Objective defines concrete use cases (httpd, MariaDB, Postgres), builds a feedback pipeline that installs use-case images and reports package lists, dependency graphs and sizes (prototype runs daily and takes ~4 hours), and finds concrete surprises: a Fedora container base plus httpd is 243 MB versus 79 MB on an empty base (≈164 MB difference), a generated dependency SVG was 1.6M lines / 113 MB, and a 35 MB minimal image is achievable; work focuses on preventing growth, removing unnecessary RPM deps and splitting systemd user- requirements.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:43Fedora Objective
- 1:05Discovery Phase
- 3:10What's the point of Linux distros?
- 6:35Define use cases
- 14:18Multiple implementations of the same functionality
- 15:41Implement process and policy changes
- 16:06Packagers Minimization Mindset - adding a dependency can have a huge impact
- 16:26Help improve Feedback Pipeline
related talks
23mCreate your own custom Fedora IoT images
16mHow to intelligently pack OS in a container image?
14mFedora on RISC-V
37mLearn about Linux, containers, and networking through self-hosting
25mCreate your own Fedora image & push it to cloud
26mContainerize your Primary Workstation! - Fedora Silverblue
28mFedora CoreOS - best host for your containers
48mFedora CoreOS: architectural walkthrough
