containerd Packaging: Who Should Ship and How?
Talkat Maintainer Summit India 2024 · on Tuesday, 2024-12-10· at 13:25· Convention Centre | Level 4 | Room 404·
summary
Project ships release tarballs only, not official debs/rpms, to minimize maintainer load; vendors and distros compile custom builds and patches (Docker, Google, Ubuntu, AWS) which fixes local deps but creates surprises like Ubuntu accidentally publishing 2.0-rc3 instead of 1.7.19 and past RHEL7 symbol mismatches. Bundled runc is removed in 1.6/2.0; upstream provides static runc binaries while vendors prefer dynamic linking for licensing/patch reasons. Builds and tests run on OBS packaging or GitHub Actions on Ubuntu, and distro scale raises significant hosting and testing costs.
AI-written summary · about
chapters (12)
- 0:00Container packaging challenges
- 1:48Why packaging is necessary
- 3:16Distribution methods
- 4:44How containerd ships upstream
- 6:08Vendor vs distribution packaging
- 8:36Dynamic vs static linking
- 11:09Vendor vs project packaging
- 13:21Project-led distribution challenges
- 15:49Bundled dependencies in 2.0
- 17:36OBS for open source packaging
- 19:19Packaging and distribution discussion
- 21:49Closing remarks
related talks
31mcontainerd Introduction and Deep Dive
30mBuilding Linux Distributions for Fun and Profit
54mStill packaging like it's 1999?
16mTaming the Linux Distribution Sprawl: A Journey to Standardization and...
18mUsing Systemd to Ship Container Runtimes. How?
56mPackaging Rust for Debian
30mSoftware Collections – when you need all the versions
26mLinux distributions, lifecycles, and containers