Hacker News Reader

What's the general consensus on the relevance of systemd when you've migrated to a fully containerized architecture? I know that I run almost everything in docker nowadays and barely touch systemd. I use fargate on AWS too and there is no systemd to touch. I use a simple python based init process inside most of my containers.

View on HN

If you are not using systemd, it is not relevant.

To be more specific, is it worth learning nowadays?

Depends on your job I would say. If you're a swe and youre pushing your own app to prod via containers then you can pretty safely ignore it.

If you're in ops and you're mostly managing that fleet but you also have to look after some non-docker stuff (say, an old artifactory or some qa tool or other) then probably the time to learn how it works is before it breaks.

My 0.02$ -- If you can avoid it, do so.

For DevOps, yes. Systemd can be a simpler solution than say Docker for some applications.

I've used systemd to great effect managing docker containers. Systemd can order the start up/shutdown of containers with other dependencies, the most common one being network file systems that are used as volumes. a very simple and clean unit file can ensure that the container is only started after the file system is mounted, and that it is killed before the file system is unmounted.

Reply on news.ycombinator.com