Docker Compose Isn't Enough
blog.tealok.tech
Docker Compose Isn't Enough
1–10 of 208 posts
Re: Docker Compose Isn't Enough
#2[flagged]
Re: Docker Compose Isn't Enough
#3Curious! I think of docker-compose as squeezing a cluster onto a workstation—not exactly a tool you'd look to for anything other than home servers or conveniently-low workloads.
Re: Docker Compose Isn't Enough
#4Definitely burying the lede that Tealok is building an alternative to docker compose. Interesting
Re: Docker Compose Isn't Enough
#5No mention of Kubernetes (and k3s, etc.)
Re: Docker Compose Isn't Enough
#6Curious! I think of docker-compose as squeezing a cluster onto a workstation—not exactly a tool you'd look to for anything other than home servers or conveniently-low workloads.
Speaking as someone who has deployed docker-compose apps to hundreds of servers at one company... It's fine. Depends what you're doing.
Re: Docker Compose Isn't Enough
#7Shameless plug: I’m building https://canine.sh as a way of turning any managed kubernetes cluster into something as easy to use as Heroku.
It’s been super frustrating in the past to be stuck on expensive PaaS vendors, but then rolling a deployment solution from scratch ended up with us trying to stitch together GitHub actions.
Been just using canine for my own projects and I’ve been able to host 4 rails & 1 Rust app pretty seamlessly with it on a $24/month digital ocean server. Would love any feedback!
Re: Docker Compose Isn't Enough
#8I've always understood docker-compose to be a development or personal tool, not for production. Is that not usually the case?
Also aside, "docker compose" (V2) is different from "docker-compose" (V1) [0], it was rewritten and integrated into docker as a plugin. It should still be able to handle most old compose files, but there were some changes.
Re: Docker Compose Isn't Enough
#9Definitely burying the lede that Tealok is building an alternative to docker compose. Interesting
It's called content marketing. IMO this article is content marketing done right since it has useful information even if you don't read to the end.
Re: Docker Compose Isn't Enough
#10I've always understood docker-compose to be a development or personal tool, not for production. Is that not usually the case? Also aside, "docker compose" (V2) is different from "docker-compose" (V1) [0], it was rewritten and integrated into docker as a plugin. It should still be able to handle most old compose files, but there were some changes. [0] https://docs.docker.com/compose/releases/migrate/
For many people self-hosting implies a personal server; it's not really "development" but it's not "production" either. In that context many people find k8s or other PaaS to be too heavyweight so Docker Compose is pretty popular. For more production-oriented self-hosting there are various newer tools like Kamal but it will take a while for them to catch up.