Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I hate that systemd refuses to work in a chroot. With all those extra services in systemd like dns, it's impossible to run in a container or chroot... And the developers blatantly refuse to fix that.


dns, network and ntp services are run in separate processes. These processes are sandboxed in a more effective manner than chroot (namespaces, capabilities, etc.). Moreover, systemd itself relies heavily on Linux sandboxing tools (like cgroups).


Isn't systemd-nspawn useful for this case? It was specifically designed to replace the need for chroot on systemd systems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: