Kata containers and qemu-mini in Fedora
summary
Packaging Kata Containers for Fedora exposes concrete problems: the runtime splits into five RPMs (runtime, builder, agent inside the image, proxy, shim), upstream Go modules force nonstandard build fixes and go-to-rpm tricks, and cgroupsv2 requires reboots or remounts on rawhide. SELinux currently must be disabled for some workflows, virtio performance needs a recent kernel and virtiofs support, and a stripped qemu-mini cuts qemu from ~13 MB to 5.8 MB but yields only unclear startup-speed gains.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:35Put containers in virtual machines
- 1:28How do you run Kata Containers?
- 2:32Installing Kata Containers
- 4:17Kata configuration
- 7:40Hypervisor configuration
- 9:15Preliminary Words of Wisdom
- 11:50A pre-history of software boxing
- 13:46The cost of control
- 15:05A simplified overview
- 19:35How Docker talks to containers
- 20:04Digression: crun vs.runc
- 23:15Swapping the runtime
- 23:26There is more than the runtime
- 26:13Bits and pieces to start with
- 28:24Kata package structure
- 29:30A tale of two package managers
- 35:58Many major issues to address
- 40:44gemu-mini: Tuned for Kata
- 43:17gemu-mini: What do we gain?
- 44:50gemu-mini: Willit ship?
- 46:29In conclusion...
related talks
27mDay 2 Keynote Sessions
45mLinux on RISC-V--Fedora and Firmware in practice
19mLinux on RISC V Fedora and Firmware Status Update
52mGetting Started with Fedora CoreOS
01h 08mUnderstanding, Building and Researching Minimal (and not so minimal) Linux Systems
28mFedora CoreOS - best host for your containers
16mMulti-Arch FedoraCI container builds with OKD
23mCreate your own custom Fedora IoT images