Docker Compose
Docker tool for defining and running multi-container applications from a YAML file.
Liked for running home-server and self-hosted services1234 and local dev stacks with one consistent, low-maintenance setup per app.5678 Complaints are scattered rather than shared:91011 containers that fail silently and leave stacks incomplete, workarounds for missing features, and brief downtime during deployments.121314
Why people recommend it
Homelab self-hosting · 3
Commenters run many personal and home services with it, from game servers to home automation.
“I use docker compose on almost every personal project - like a minecraft server for my kids, home automation, AI hacks, etc.”
“I have a dedicated server at the house where I run nearly a dozen services via docker compose.”
Show 1 more
“finally `ssh homelab "cd /opt/<homelab>/stacks/<app> && docker compose up -d"`, and I couldn't be happier to tinker to my heart's desire.”
Local dev stacks · 3
Used to spin up local development and QA environments with web servers and databases.
“I'm generally running my local dev stack with Docker compose. Not always, but I use it in a lot of projects.”
“I've used basically the same docker compose setup for all my projects that aren't large distributed systems in the last 10 years.”
Show 1 more
“it's a godsend for setting up a local dev machine or something like that”
Consistent setup · 3
One repeatable pattern for every app makes deployments quick, reliable and low-maintenance.
“I use Docker Compose so that I don't have to care if the daemon is a single binary or a whole stack”
“I've used basically the same docker compose setup for all my projects that aren't large distributed systems in the last 10 years.”
Show 1 more
“moved to hosted debian with docker-compose and neveer had a breakage”
Single-box deploys · 3
Easy to set up and update small projects on one VPS or home machine.
“I use docker compose a lot for small projects on a single box like Ovh vps.”
“installing docker compose on it”
Show 1 more
“I used to use DOCKER_HOST=ssh… with compose for years, very solid.”
Readable config · 3
Projects ship ready-to-use compose files that also document the architecture and replace custom scripts.
“most projects provide a ready to use compose file that you can copy paste”
“I love reading the compose file when a project has it. It is the quickest way for me to get a high level idea of this project's architecture.”
Show 1 more
“a docker compose is even better to mitigate incantations”
Reverse proxy fit · 3
Pairs easily with Traefik or Caddy for routing, TLS and auth.
“I also find compose hits the sweet spot for integration into my homelab”
“I use Docker Compose so that I don't have to care if the daemon is a single binary or a whole stack”
Show 1 more
“for "web apps" I'll pretty much containerize all the things”
Caveats and dissent
Silent failures · 1
One commenter warns a failed database container can silently leave a stack incomplete.
“Do not go the compose route (that route is filled with sadness of the incomplete stacks because db container failed silently kind)”
Missing features · 1
One commenter finds it needs complicated workarounds compared with Kubernetes.
“I actually struggle with compose ('orchestration' alternative) significantly more since it usually has complicated workarounds to missing features.”
Deploy downtime · 1
Remote deploys over DOCKER_HOST=ssh cause a little downtime.
“I used to use DOCKER_HOST=ssh… with compose for years, very solid.”
Scattered YAML · 1
One commenter finds compose files hard to locate and their labels under-specified.
“docker compose files are weird blobs of YAML that I have to hunt down the location of”
Overuse · 1
Splitting a simple private app across many containers can make logs and configs harder to reach.
“it's a godsend for setting up a local dev machine or something like that”
Often compared with
3 moved from Docker Compose to Quadlet
1 moved from Kubernetes to Docker Compose
1 moved from Docker Compose to Podman
1 moved from NixOS to Docker Compose
1 moved from Docker Compose to process-compose
1 moved from Coolify to Docker Compose
Who recommends it in their own words
Threads where it came up
- What I self-host 6 mentions
- Should I Run Plain Docker Compose in Production in 2026? 5 mentions
- Docker is weird 4 mentions
- Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes 2 mentions
- NixOS is making me less afraid 1 mention
- I paid people to try and follow my README 1 mention
Data: docker-compose.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 37
“it's a godsend for setting up a local dev machine or something like that”
“I've really been enjoying using AI to write docker/compose config and related ad hoc scripts.”
“I'm generally running my local dev stack with Docker compose. Not always, but I use it in a lot of projects.”
“I use docker compose on almost every personal project - like a minecraft server for my kids, home automation, AI hacks, etc.”
“moved to hosted debian with docker-compose and neveer had a breakage”
“Otherwise I'm using the same docker compose setup I've been using for a while!”
“most projects provide a ready to use compose file that you can copy paste”
“I use Docker Compose so that I don't have to care if the daemon is a single binary or a whole stack”
“I've used basically the same docker compose setup for all my projects that aren't large distributed systems in the last 10 years.”
“I also find compose hits the sweet spot for integration into my homelab”
“I love reading the compose file when a project has it. It is the quickest way for me to get a high level idea of this project's architecture.”
“a docker compose is even better to mitigate incantations”
“Vagrant for VM provisioning and OS dependencies only. docker-compose for the rest”
“ideally is in docker compose and defined in code”
“I have a dedicated server at the house where I run nearly a dozen services via docker compose.”
“one week ago switched from a Debian to NixOS setup, using docker compose”
“Do not go the compose route (that route is filled with sadness of the incomplete stacks because db container failed silently kind)”
“run my docker compose”
“for "web apps" I'll pretty much containerize all the things”
“It's been a super solid tool overall, and I'm pretty happy with it.”
“I used to use DOCKER_HOST=ssh… with compose for years, very solid.”
“docker compose files are weird blobs of YAML that I have to hunt down the location of”
“I use docker compose a lot for small projects on a single box like Ovh vps.”
“I love it so much I have created a thin statless orchestrator layer upon it”
“I used a docker compose approach.”
“installing docker compose on it”
“I actually struggle with compose ('orchestration' alternative) significantly more since it usually has complicated workarounds to missing features.”
“The entire stack is containerized with Docker Compose”
“I used to be very enthusiastic about docker compose”
“Usually a project will have a docker compose with web server, database etc.”
“Then you didn't need Kubernetes in first place.”
“I just spent time getting it all running on docker compose”
“just have a docker-compose.yaml and then just docker-compose it to start it”
“having a local stack easily spun up via docker compose is nice”
“finally `ssh homelab "cd /opt/<homelab>/stacks/<app> && docker compose up -d"`, and I couldn't be happier to tinker to my heart's desire.”
“My Docker compose setup has moved from Arch to Ubuntu to NixOS now”
“I have a pipeline in Docker compose”