Skip to content

Developer tools · container orchestrator

Docker Compose

Hacker Approved

Defines a whole multi-container app in one declarative YAML file, making local dev and single-server deployments quick and repeatable; critics find it awkward for production, rootless and multi-host setups.

Summarized from 235 comments.

Defines a whole multi-container app in one declarative YAML file, making local dev and single-server deployments quick and repeatable; critics find it awkward for production, rootless and multi-host setups.

recommend
149
criticize
44
months recommended
12 of 13
median owned, 3 owners said
5 years

Why people love it

  • Whole stack in one YAML · 6

    Having your whole application with its containers, volumes, and networks all defined together in one easy-to-read YAML file is a way better experience.

    May 2026 · comment

    I like running docker compose for my simple needs because it consolidates pretty much all the config in one declarative file

    May 2026 · comment

    the ability to use YAML for declarative configuration is the most critical feature for any container tool

    Jun 2026 · comment
  • Simple, quick deploys and redeploys · 7

    I use docker-compose mainly because it's so "easy" to just ssh into the machine and run something like "git pull && docker-compose up"

    Mar 2026 · comment

    I can use the same setup for everything, and deploying an entire new thing in a maintainable way is quick and easy.

    Oct 2026 · comment

    having a pre-made docker compose means I can throw it on my general app VM and it'll take 5 seconds to spin up

    Dec 2025 · comment
  • Enough for single-server production · 6

    Docker running through Compose can handle few hundreds of thousand of users per day without an issue

    May 2026 · comment

    You could setup a docker compose on 1 single decent server and call it a day when you have 0 users.

    Dec 2025 · comment

    If you can confidently get it done with docker-compose, you shouldn't even think about using k8s

    Nov 2025 · comment
  • Great local multi-service dev loop · 5

    there's nothing as idiot proof as docker compose that works on windows/mac/linux/whatever the new guy prefers to run

    Aug 2026 · comment

    it's hard to beat compose for a tight dev loop of multiple dependencies in a micro-service architecture

    May 2026 · comment

    You can easily mount extra directories from your developer host machine in read or read+write mode.

    May 2026 · comment

What people warn about

  • Friction in non-local deployments · 4

    Compose is great, but a couple things always created friction for me when using it for non-local setups

    May 2026 · comment

    I feel it lacks when it comes to deployment, especially when using it rootless or on rootless images.

    Nov 2025 · comment

    I love the ease of using databases in docker compose as well but I always worry about production

    May 2026 · comment
  • Docker/Podman/version behavior inconsistencies · 4

    compose overlay files merged list values differently between the Docker and Podman versions, which was a PITA in teams running Docker & Linux dev machines

    May 2026 · comment

    Ever had "docker compose" and "docker-compose" do subtly different things which drive your team mate to pull their hair out?

    May 2026 · comment

    compose itself behave in unexpected ways, weird things like not realizing the tag of an image it is running

    May 2026 · comment
  • Networking limits and security concerns · 2

    Docker compose assumes all your services can reach each other over docker, which I find horribly insecure.

    May 2026 · comment

    The networking aspect of it still isn't feature-compatible compared to using docker.

    Jul 2026 · comment
  • YAML files hard to follow · 2

    docker compose files that are way more difficult to understand than the equivalent K8S manifests

    Dec 2025 · comment

    docker compose files are weird blobs of YAML that I have to hunt down the location of

    May 2026 · comment

What hackers pick instead

Every quote

The 40 most detailed of 235 comments. Each links to the original.

  1. Having your whole application with its containers, volumes, and networks all defined together in one easy-to-read YAML file is a way better experience.

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  2. I use docker-compose mainly because it's so "easy" to just ssh into the machine and run something like "git pull && docker-compose up"

    Recommends · Mar 2026 · in “A Decade of Docker Containers”

  3. I like running docker compose for my simple needs because it consolidates pretty much all the config in one declarative file

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  4. there's nothing as idiot proof as docker compose that works on windows/mac/linux/whatever the new guy prefers to run

    Recommends · Aug 2026 · in “Meta Security Researcher's AI Agent Accidentally Deleted Her Emails”

  5. I can use the same setup for everything, and deploying an entire new thing in a maintainable way is quick and easy.

    Recommends · Oct 2026 · in “What I self-host”

  6. Pleasantly surprised at how well we can deterministically produce larger k8s apps configs from the compose spec.

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  7. having a pre-made docker compose means I can throw it on my general app VM and it'll take 5 seconds to spin up

    Recommends · Dec 2025 · in “Self-hosting my photos with Immich”

  8. Using Docker Compose lets us keep everything versioned and spin up or redeploy the whole stack in seconds.

    Recommends · Apr 2026 · in “I rebuilt the same project after 15 years – what changed in web dev”

  9. Docker compose assumes all your services can reach each other over docker, which I find horribly insecure.

    Mixed · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  10. the ability to use YAML for declarative configuration is the most critical feature for any container tool

    Recommends · Jun 2026 · in “macOS Container Machines”

  11. Compose is great, but a couple things always created friction for me when using it for non-local setups

    Mixed · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  12. it's hard to beat compose for a tight dev loop of multiple dependencies in a micro-service architecture

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  13. you can deploy your application on-premises, in the cloud, or at a customer site with a single command

    Recommends · Nov 2025 · in “You want microservices, but do you need them?”

  14. Docker-compose isn't a backup, but from a fresh ubuntu server install, it'll have me back in 20 mins.

    Recommends · Mar 2026 · in “My Homelab Setup”

  15. I feel it lacks when it comes to deployment, especially when using it rootless or on rootless images.

    Mixed · Nov 2025 · in “Automating rootless Docker host updates with Ansible”

  16. Docker running through Compose can handle few hundreds of thousand of users per day without an issue

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  17. You can easily mount extra directories from your developer host machine in read or read+write mode.

    Mixed · May 2026 · in “Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs”

  18. using the compose yaml file to document what should be running is pretty powerful at smaller scales

    Mixed · Dec 2025 · in “Show HN: Mushak – Zero config zero downtime Docker/Compose to server deployment”

  19. You could setup a docker compose on 1 single decent server and call it a day when you have 0 users.

    Recommends · Dec 2025 · in “Google Cloud Run cost me $4,676 in 6 weeks with zero traff”

  20. Each worktree gets its own docker compose project name so they can run docker stacks in parallel.

    Recommends · Jul 2026 · in “Git worktrees are not an isolation boundary for coding agents”

  21. If you can confidently get it done with docker-compose, you shouldn't even think about using k8s

    Recommends · Nov 2025 · in “Helm 4.0”

  22. I love the ease of using databases in docker compose as well but I always worry about production

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  23. You can set it up with docker compose and put the container on the same network of your dev env

    Recommends · Feb 2026 · in “Pg-dev-container is a ready-to-run VS Code development container for PostgreSQL”

  24. If the project fits on a single server (which it probably can in 2026) docker compose is great.

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  25. Docker compose is fine for running a small internal service in production for dozens of users

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  26. Just move your compose files and zip the mount folders and you can move stuff easily enough.

    Recommends · Feb 2026 · in “Tech Independence”

  27. gave me 95% of what I wanted and the complexity was basically one file with few surprises

    Recommends · Nov 2025 · in “Helm 4.0”

  28. compose just feels so much better as abstraction especially with small and medium setups

    Recommends · Apr 2026 · in “Dear friend, you have built a Kubernetes (2024)”

  29. It is the quickest way for me to get a high level idea of this project's architecture.

    Recommends · Oct 2026 · in “What I self-host”

  30. compose overlay files merged list values differently between the Docker and Podman versions, which was a PITA in teams running Docker & Linux dev machines

    Criticizes · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  31. the docker compose model quickly becomes a lot of messy brittle squeeze for little gain when multiple containers need to integrate

    Criticizes · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  32. Ever had "docker compose" and "docker-compose" do subtly different things which drive your team mate to pull their hair out?

    Criticizes · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  33. compose itself behave in unexpected ways, weird things like not realizing the tag of an image it is running

    Criticizes · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  34. have to run a whole separate podman service to lie to docker compose about not actually being docker

    Criticizes · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  35. docker compose files that are way more difficult to understand than the equivalent K8S manifests

    Criticizes · Dec 2025 · in “Uncloud - Tool for deploying containerised apps across servers without k8s”

  36. docker compose files are weird blobs of YAML that I have to hunt down the location of

    Criticizes · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  37. The networking aspect of it still isn't feature-compatible compared to using docker.

    Criticizes · Jul 2026 · in “Podman v6.0.0”

  38. containers simplify deployment and updates and isolation, and at this point I find for me the benefits more than outweigh the hassles

    Recommends · Oct 2026 · in “What I self-host”

  39. I too prefer the Docker compose route. If you give me a single binary, I'll go out of my way to run it inside a compose stack.

    Recommends · Oct 2026 · in “What I self-host”

  40. going further you often just cannot beat the simplicity of doing update QA or other CI/CD workloads in compose based projects

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

Counts from 1,795,640 Hacker News comments, Nov 2025 to Nov 2026. How we count · Report a mistake