I am using systemd + go binary deploy. Running 10 years+ in production. Meanwhile docker based setup fail every now and then. And kubernetes? well forget about it.
Do you do rolling deploys?
Should I run plain Docker Compose in production in 2026?
201–210 of 312 posts
Re: Should I run plain Docker Compose in production in 2026?
#202Earlier quoted context omitted.
Caffeine is healthy. Caffeine is unhealthy. Caffeine is healthy again. Eggs are healthy. Eggs are unhealthy. Etc etc etc. There’s a reason articles like this exist. Things change.
Well, the fashion changes. At one time, sugar too was advertised as beneficial for tooth health.
"Sugar Puffs has the energy growing kids need."
Re: Should I run plain Docker Compose in production in 2026?
#203sign... another ai written article. are we already living in the dead internet? hackernews is filled with ai written blog posts.
Re: Should I run plain Docker Compose in production in 2026?
#204I like running docker compose for my simple needs because it consolidates pretty much all the config in one declarative file, and docker manages 'everything'. By now I know how to handle the handful of caveats listed in this article. Beyond what's listed there, I'd also give a mention to the way port publishing works (the fact that it ignores firewalls), as that's something that still trips people up if they don't kn…
> I'd also give a mention to the way port publishing works (the fact that it ignores firewalls), as that's something that still trips people up if they don't know about it. Isn't that a Docker thing rather than Docker Compose though? There is a ton more caveats to add if we don't already assume the reader is familiar with the hard edges of Docker, seems the article only focuses on Docker Compose specifically, probabl…
It is yeah – I was thinking along the lines of the decision being between docker compose and something like podman quadlets
Re: Should I run plain Docker Compose in production in 2026?
#205I use docker compose a lot for small projects on a single box like Ovh vps. With a reverse proxy on the host. Nice ans easy to setup and update.
If you want to test something that is between compose and k8s, check ring: https://github.com/kemeter/ring
Re: Should I run plain Docker Compose in production in 2026?
#206Earlier quoted context omitted.
It's simple to use only for toy use cases, that's why nobody uses it. The article everyone in this thread seems to like only goes as far as 'I pushed to git so it must be ok' which is laughable and I'm not even DevOps. What happens if it errored on deployment or after that? you wanna write custom (bash? :D) hooks for that? What about upgrading your 'very vertically scalable' box? What if it doesn't come up after the…
Define production. Docker compose is fine for running a small internal service in production for dozens of users (i.e. not for developing said service, but for using it). I would assume it isn't fine to run a hyperscaler (but I wouldn't know). Those are extremes, and there are going to be a ton of situations in between. I can't personally speak to what the limit of docker compose is, as I have only worked on the lowe…
From my personal experience if deployment strategy is thought through then Docker running through Compose can handle few hundreds of thousand of users per day without an issue and probably could handle more with proper hardware upgrades.
Re: Should I run plain Docker Compose in production in 2026?
#207What I found pretty great with docker is isolating individual docker systemd instances in rootless linux namespaces (i.e. users). I wrote about this here [1].
This lets you easily create multiple services on one VM that are quite isolated from each other. This system of doing things has worked reliably for me for quite some time, even for the 'bigger' services (gitlab, nextcloud, mailcow-dockerized etc.).
[1]: https://du.nkel.dev/blog/2023-12-12_mastodon-docker-rootless...
Re: Should I run plain Docker Compose in production in 2026?
#208Compose is great, but a couple things always created friction for me when using it for non-local setups: * Lack of a user-friendly way of managing a Docker Compose installation on a remote host. SSH-forwarding the docker socket is an option, but needs wrappers and discipline. * Growing beyond one host (and not switching to something like Kubernetes) would normally mean migrating to Swarm, which is its own can of worm…
[deleted]
Re: Should I run plain Docker Compose in production in 2026?
#209Earlier quoted context omitted.
It's simple to use only for toy use cases, that's why nobody uses it. The article everyone in this thread seems to like only goes as far as 'I pushed to git so it must be ok' which is laughable and I'm not even DevOps. What happens if it errored on deployment or after that? you wanna write custom (bash? :D) hooks for that? What about upgrading your 'very vertically scalable' box? What if it doesn't come up after the…
I think people are using different meanings of “production environment.” I agree with gear54us and upvoted their comment, but I also understand what the author of the root comment is saying. I have also delivered systems using Docker Compose that are actually running in production. The point I want to make is that people may define “production” differently depending on the number of active users, operational requirem…
"Not just for my own projects but for $500 million dollar companies and more."
Seems reasonable to assume these are serious production environments, no?!
Re: Should I run plain Docker Compose in production in 2026?
#210I really want something that is Docker Compose but for Kubernetes. I mean that I can have a simple way to declaring resources in just like Docker Compose, but I run the environment in Kubernetes so that I can get to test the behaviors when there are multiple copies of the softwares running together. I do rely on Kubernetes heavily for distributed and networked software deployment, so it is even better if we can emula…
You should take a look at https://nixidy.dev/.