Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Should I run plain Docker Compose in production in 2026?

distr.sh

Post reply on HN
Print view View original

51–60 of 312 posts

Re: Should I run plain Docker Compose in production in 2026?

#51

Post by nixpulvis »

2ndorderthought wrote: post #11

Should you have a turkey sandwich for lunch in 2026? I don't know buddy just do whatever. There are ten thousand other sandwiches you could eat surely, but does turkey sound good for you?

Surely we can give more informed answers to questions like this than to compare a technical decision to the craving for a sandwich.

Comments like this are apathetic and reduce the challenges of good software engineering to hopes and random chance.

Re: Should I run plain Docker Compose in production in 2026?

#52

Post by stevefan1999 »

I 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 emulate things like latency or burstable packet loss so that we can do a controlled chaos test for reliability test. I tried Skaffold, Tilt, Devspaces and Devpod/Coder v2, none of them are really simple like Compose.

Re: Should I run plain Docker Compose in production in 2026?

#53

Post by close04 »

2ndorderthought wrote: post #18
poly2it wrote: post #17

Earlier quoted context omitted.

Is your point that we shouldn't motivate our technological choices? I wouldn't use Docker Compose in production.

Yes. I clearly believe we should not motivate choices in technology.

But then if you're not going to answer a question on technology, and you won't motivate any of the choices, including the one to not give an answer, what's the value in participating to the conversation?

Your entire original comment looks like just an opportunity to be snarky. It's a longer version of "whatever", which you can literally throw around as an answer to anything.

In case you were curious, the subheading of the article already answers the question posed by the title:

> Yes, plain Docker Compose can still run production workloads in 2026—if you close the operational gaps it leaves: cleanup, healing, image pinning, socket security, and updates.

Re: Should I run plain Docker Compose in production in 2026?

#54

Post by b40d-48b2-979e »

malux85 wrote: post #40
JodieBenitez wrote: post #33

Earlier quoted context omitted.

I wouldn't use Docker in production.

Spotify, Visa, NASA, Netflix, and a zillion others do, why not?

They are not using Docker at runtime for their services. Every company uses Docker for builds unless they have a particular cost or ethos they're avoiding and purely using Linux/podman/buildah/et al.

Thinking about it a little further, though, I believe Rancher Desktop has come a long way and may be eating market share.

Re: Should I run plain Docker Compose in production in 2026?

#55

Post by JodieBenitez »

malux85 wrote: post #40
JodieBenitez wrote: post #33

Earlier quoted context omitted.

I wouldn't use Docker in production.

Spotify, Visa, NASA, Netflix, and a zillion others do, why not?

I just never felt the need for it. I'm not saying it's bad (I really don't know), it's just one of these things that solve problems I don't have.

Re: Should I run plain Docker Compose in production in 2026?

#57

Post by merpkz »

How do you guys, who run Docker in production deal with managing nftables firewall on hosts running containers? By design docker daemon creates and manages a set of firewall rules to forward traffic between containers and ingress traffic into containers as well as masquarades the outgoing container traffic. That is all well until admin needs to alter hosts firewall to allow and deny other traffic unrelated to docker - and restarting nftables or even applying new nftables rules usually ( flush ruleset in /etc/nftables.conf ) purges all the docker created rules and effectively breaks everything until docker daemon is restarted and rules re-created. I have partially solved this by using nftables filter chains with different names - admin_input/admin_output and using input hook with negative priority - so that traffic I choose to block is evaluated before docker rules are applied - that feels a bit like hack, but so far is the only way I have found. It is good practice in this day and age to run local firewalls on all hosts with policy deny, so that only traffic explicitly allowed can pass, that can severely limit blast radius during compromise.

Re: Should I run plain Docker Compose in production in 2026?

#58

Post by TheCapeGreek »

Somewhat adjacent in how I look at using Docker at all in prod, here's what I always wonder:

Is using Docker/Compose "just" as the layer for installing & managing runtime environment and services correct? Especially for languages like PHP?

I.e. am I holding it wrong if I run my "build" processes (npm, composer, etc) on the server at deploy time same as I would without containers? In that sense Docker Composer becomes more like Ansible for me - the tool I use to build the environment, not the entire app.

For the purpose of my question, let's assume I'm building normal CRUD services that can go a little tall or a little wide on servers without caring about hyper scale.

Post reply on HN