Ask HN: A Better Docker Compose?
Docker compose is a dead end AFAIK, it&#x27;s not deprecated or anything, but the community power behind it has essentially moved to other things (Kubernetes, but also wasmer, nomad, skaffold).<p>While Docker Desktop &#x2F; Podman &#x2F; Rancher Desktop combined with stuff like Skaffold aren&#x27;t exactly a drop-in replacement for docker-compose, it does do a much better job at bringing up and tearing down entire compositions while re-using existing packaging and access controls.<p>If you are running docker-compose for non-development things, it might be a different story; it might be suitable for non-GitOps things, but as posted elsewhere, at that point you&#x27;re better off using something like systemd.<p>When composing really small setups I either do this with a shell script (think 10 lines including trapping exits) or a systemd unit. Whenever it needs to be bigger I nearly always end up with an actual scheduler (K8S, Nomad) and GitOps because you can&#x27;t really deliver something maintainable, available and durable anymore without it (well... I suppose if you have only 1 project to deliver, forever, you could manually manage it).<p>It does get a whole lot easier when you have a common foundation you can re-use. Spinning up an entire stack with security, monitoring, alerting, automatic rollouts&#x2F;rollbacks for even the smallest project is just single-digit minutes work now.<p>Pulling in some other factors: how sharable&#x2F;collaboratable is something these days if it is not built on similar enough technologies and modules? A solo yolo project might not care much about this, but when was the last time someone asked for software that is risky and not durable?