[qwertyuiop924]

Wrong. Docker manages containers, and only containers. 'docker logs' shows you the logs from your containers. Docker never tried to make me run my non-container logs through 'docker logs'. You know what else docker never tried to be? cron. Or udev. Or consolekit. Or init. It just tries to manage your containers.

[Etzos]

I think this is a little bit off. You're looking at them from two different perspectives.

Docker wants to manage your containers. And in that regard it is one monolithic daemon that manages everything about your containers.

Systemd wants to manage your computer and things related to init. It is a bunch of modular, but strongly integrated, pieces that manage everything about your init and process management.

[qwertyuiop924]

>>It is a bunch of modular, but strongly integrated, pieces that manage everything about your init and process management.

OH REALLY? well, can I just run systemd-udevd, without systemd? how about journald? No? well than, if everything depends on one massive daemon, it isn't very modular, is it.

[JdeBP]

The correct answer is actually "Yes, you can.".

[qwertyuiop924]

Not soon. You can't run journald without systemd now, and you won't be able to run systemd-udevd without systemd as soon as kdbus gets merged, which the systemd devs are pushing for heavily.

[JdeBP]

Your information is out of date with respect to systemd-udevd, per https://news.ycombinator.com/item?id=10518933 and others; and your assertion about journald is simply wrong unless something has changed very recently.

[qwertyuiop924]

Also, cron isn't init and process management. Udev isn't init and process management. Neither is consolekit.