Hacker News Reader

To all the people pointing out that docker compose doesn't scale, I use docker compose locally in a vs code dev container and then k8s on production. Running k8s locally seems too complex, maybe it's not so bad but I'm happy with using docker compose dev container for development

View on HN

To me, docker compose is simply a more readable way of running docker commands; anything you can do with the docker cli, you can run as a docker compose file.

Just like how a shell script is easier to manage than stringing lots of commands in the terminal, defining services in yaml is easier to manage than adding a million flags to your docker commands.

Of course at a certain point you may need further abstractions, but I agree with you that these should only be used if they're actually needed.

I have no idea why anyone would want to run K8s locally. The concept makes absolutely no sense to me.

If you want to run a container, just run the container? K8s is here for scaling, not for running stuff in local.

What if you need to run 20 services simultaneously? You would either need to maintain two sets of configuration for kubernetes and compose or use just one kubernetes configuration both for production/staging and local development.

Reply on news.ycombinator.com