4 ms·

Acutally, there are docker-compose primitives that solve just that (restart: always/on-failure and depends-on: servicename. I think it mostly comes down to wha

Acutally, there are docker-compose primitives that solve just that (restart: always/on-failure and depends-on: servicename. I think it mostly comes down to what layer of abstraction you like working at.

BossingAround 3y ago
Podman can generate systemd units for managing containers IIRC.
- MonkeyClub 3y ago
  Yep, that's right: https://docs.podman.io/en/latest/markdown/podman-generate-systemd.1.html https://docs.podman.io/en/latest/markdown/podman-generate-sy...
stryan 3y ago
Problem is you can't have it depend on anything outside of docker i.e. I can't write a docker-compose file that waits for an NFS mount.
spenczar5 3y ago
True, Docker-compose has a lot more overlap with systemd. But it doesn’t have system-level dependencies. For example, in systemd I can wait for a network interface to be up and have an IP assigned by DHCP. As far as I am aware, docker compose knows about the docker network and its own containers, but not the system more broadly. Also, you will likely want it to run for a long time, so something has to trigger the docker-compose process to start and restart it. You might want it to restart in case the OOM killer knocks it over. That daemom stuff is what systemd is good for.