Reviving (un)schroot?
summary
Compares the existing schroot backend and a newer unshare backend for sbuild, naming unshare as addressing convenience, security, and reproducibility but introducing downsides by embedding a container runtime and breaking some schroot use cases. Presents a proof-of-concept that exposes unshare-style improvements through the schroot API, describes its current limitations, and asks for feedback on required features to make that approach practical.
AI-written summary · about
related talks
11mImmutable Linux systems and how they work
30mRootless, Reproducible, and Hermetic: Secure Container Build Showdown
54mContainers unplugged: understanding user namespaces
30mWhat’s Under the Hood of Docker? Process Separation in the Linux kernel
21m{slushy}: A Bridge to the Future
37mDocker without docker- understanding the basics
41mDelta Updates: Making Updates Leaner
32mTake Control of your Filesystems with containerd’s Snapshotters - Stephen Day, Docker, Inc.