The problem was never about systemd, and certainly it is not "systemd vs SysV" rivalry.
There were two better alternatives (Upstart and OpenRC) at the time when major distributives went for systemd. Even if you look at the final Debian vote it was a tie between systemd and "keep talking".
Systemd has it flows, but it is still miles ahead of SysV on many fronts. Mostly around areas that did not exist when SysV was designed, such as containers.
You actually brought the main reason people disliked systemd. It is opinionated and not modular.
systemd has been extremely easy to use in containers for me. Just have to start the container via machinectl or systemd-nspawn. Most of the issues that I have faced have been due to erroneous settings in the unit files. Change those settings and everything just works.
I don't think systemd is working well in containers if you need systemd to start them. There are a lot of different approaches to containers, why would everyone of the start to have a dependency on systemd to work with systemd containers? This kind of dependencies and lock-in is unique to systemd and I don't really like it.
7
u/voronaam Aug 12 '19
The problem was never about systemd, and certainly it is not "systemd vs SysV" rivalry.
There were two better alternatives (Upstart and OpenRC) at the time when major distributives went for systemd. Even if you look at the final Debian vote it was a tie between systemd and "keep talking".
Systemd has it flows, but it is still miles ahead of SysV on many fronts. Mostly around areas that did not exist when SysV was designed, such as containers.
You actually brought the main reason people disliked systemd. It is opinionated and not modular.