Simon McVittie proposes some alternatives: > I would personally suggest podman
podman is perhaps often a good choice. However, sometimes it can be useful or even essential to use a setup with *less* isolation. That is often the case for me. I have multiple situations where I want to use software in a chroot and *allow* it access to my normal home directory, full process tree, and so on. > Or, for sbuild users, the unshare backend autopkgtest-virt-unshare(1) The autopkgtest-virt-unshare backend seems quite primitive compared to schroot. schroot offers user-switching and an intermediate level of privsep. This is a feature that can be useful. It is also highly configurable. Also, it hasn't had the level of testing and maturity that the schroot backend has. (When I first tried it out it I discovered a howler bug.) I don't think these are realistic replacements for schroot. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
