4 ms·
Because, systemd is like a mafia in modern(!) linux distros, you have to pay tribute to it by integrating with it, because it is an all controlling daemon. Not
by CSDude 10y ago
Because, systemd is like a mafia in modern(!) linux distros, you have to pay tribute to it by integrating with it, because it is an all controlling daemon. Not trying to flamewar here, but as you do, I really dont understand why we need to have systemd integration for just doing anything.
- tadfisher 10y agoSome advantages: - I can use the same tools to administer both host and guests (systemctl and journalctl). - cgroups and namespaces are managed the same way on both host and guests. - I can integrate containers (via .nspawn and .service units) with my host init/supervision daemon, like any other systemd service, without translating from one configuration format to another. - Because of the above, resource/quota constraints for a single container or groups of containers can be described via a common configuration.
- sjellis 10y agoYeah, there's an underlying point here that containers are just processes, so there should be little difference between containerized services and services running directly on the host. There's an idea that the desired end-state should be that all services are containerized, which means that either Docker manages services (as in RancherOS), or systemd does.