Systemd-Nspawn is Chroot on Steroids
summary
systemd-nspawn creates a bootable container by creating a distro root with yum or debootstrap and then running systemd-nspawn -b -D to boot it, showing a full systemd inside P1; machine listing and control use machinectl/cgls to inspect cgroup hierarchies and merged journals (journalctl -M). demo works but hits three concrete issues: a kernel bug that fails to notify container exit (leaked machine names), audit subsystem incompatibility (workaround audit=0), and a Fedora packaging bug missing the /var/run → /run symlink.
AI-written summary · about
chapters (13)
- 0:00Introduction to nspawn
- 2:00Purpose and design
- 6:08Nspawn vs other tools
- 9:30Creating container images
- 13:15Booting and using containers
- 16:53Process hierarchy
- 18:55Cgroups and monitoring
- 22:14Networking and journal
- 24:33Machine control
- 30:28Kernel bugs and limitations
- 36:06Advanced nspawn features
- 39:26Container configuration
- 46:14Questions and answers
related talks
19mJoins
36mSystemd, from /dev/null to root
37mDocker without docker- understanding the basics
18mUsing Systemd to Ship Container Runtimes. How?
44mThe Containerization of the Operating System: Exploring Bootc and the Future of Linux Deployment
22mWhat's new in systemd in 2016?
41mReproducible, Immutable, Bootable: Exploring bootc with Podman Desktop
38mWe Need to Talk About Systemd: Boot Time Optimization for the New init daemon