A whirlwind tour of systemd-nspawn containers (2025)
ibobev
42 points
7 comments
October 23, 2026
Related Discussions
Found 5 related stories in 361.3ms across 10,409 title embeddings via pgvector HNSW
- The state of systemd: 2026 edition hnrprtlpdb · 15 pts · October 10, 2026 · 57% similar
- Linux containers in 500 lines of code (2016) mkornaukhov · 113 pts · October 05, 2026 · 52% similar
- Systemd Linger edward · 61 pts · July 26, 2026 · 47% similar
- Systemd is a suite of basic building blocks Bluestein · 35 pts · September 18, 2026 · 46% similar
- Show HN: Drop – A rootless Linux sandbox with gVisor support mixedbit · 162 pts · September 22, 2026 · 45% similar
Discussion Highlights (4 comments)
lifeisloving
Per the other blog post on docker. Docker Iptable bs has been annoying me for the last 48, hours. It actually makes no sense.
chasil
Eleven years ago, I wrote an introduction to nspawn from a busybox perspective. https://www.linuxjournal.com/content/infinite-busybox-system... I used that for a number of designs before my retirement. The quality of my writing certainly did improve after that was finished.
ectoloph
I have been using systemd-nspawn recently through NixOS containers[1]. The combination feels quite powerful if you are in the ecosystem. Though it is slightly ironic that I find Nix more approachable with the help of LLMs and then Nix has become one of the ways I manage the environments for the LLMs. [1] https://wiki.nixos.org/wiki/NixOS_Containers
noopprod
I found a bug with nspawn that it can't bind mount while being in the mode which lets you delegate namespaces or whatever Aka If you have some kind of mount that matters like NVIDIA, you can't also create containers from containers. So I just switched to LXC but I guess I should submit a slop PR as well. But yeah I guess Id just caution anyone who was going to use it lol