Hi Claudius,
I see that you are using schroot. How is your progress on 'sudo' removal?
schroot itself, doesn't solve the 'sudo' problem, but it's very useful for running common tasks when setting up a chroot, like mounting filesystems, setting up binfmt etc.
So basically it extends the chroot command itself.
I haven't heard of schroot before, but from what I gather it needs a
privileged service to run in the background.
I've never heard about or noticed that schroot needs a privileged service running in the background. Maybe I have to check this.
The main cause for introducing the schroot feature, was to have a already implemented framework, when setting up chroots (mostly related to setting up mounts).
Since a lot of chroot tasks running in parallel, if searched for a reliable chroot extension.
What are your experience with it? Could it be used for all parts that
currently require root privileges? Have you tried it inside a docker
container?
That is what I think the docker container is for solving the 'sudo' problem.
Running schroot inside a docker container is now problems and behaves exactly the same, like running it without schroot.
Regards,
Benedikt