Systemd vs. Docker

I'd say the sad part is that people still insist on writing init scripts, let alone using them in situations like this, because it demonstrates a lack of situational or historical awareness — those scripts (it'd be more correct to call them "rc scripts", but that'll never catch on) are nothing more than a layer of impedance-matching between the rigidity of sysvinit's configuration format and the desire of most distros to have a generic one-size-fits-all solution.

And once you're aware of that background, it seems all the more bizarre to try and transplant the workaround (with all its inherent downsides) into a systemd *or* docker environment, where neither side of the original problem it was supposed to solve exists!

Note that there is nothing wrong with sysvinit itself, in fact it's a perfectly serviceable PID 1 in a controlled environment like a container, where it's not buried away under a quarter-century of accumulated hacks.