[justsomehnguy]

> single node deployments

Docker Compose is for a single developer deployments [0].

Every time I mess with Compose and I need for the things to be services[1] I just give up after the some amount of reboots, YAML mangling, cursing, documentation reading, keyboard throwing. I just rebuild it as a Swarm service and it works. Till Swarm (on a single node) breaks, but this is another can of worms.

[0] On developer's machine. On developer's distro.

[1] be started after reboot, successfully start after reboot, with all dependencies. It doesn't seems like a high bar.. but Docker Compose fails at it.

[NorwegianDude]

Nothing wrong within using compose in production. As for restarts, I've never had any issues with it.

[tluyben2]

Same here. I deploy on VPSs with compose and restart works fine. Maybe there are cases in which it does not work; I have quite a lot of issues on local mac m1. But there I don’t really care as it’s easy to just kill and restart docker.

[justsomehnguy]

"I never had it a problem with N => N never happens" amirite?