Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


I also would not eat a turkey sandwich for lunch on a Tuesday.

*shudder*


I wouldn't use Docker in production.


I assume you mean Docker _daemon_

Docker also commonly refers to Docker _images_ or Docker-esque container setups


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.


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.


Most companies I’ve seen from the inside were using containerd or crio.


There are more secure alternatives. Are you sure those you listed actually use it on the servers? I would guess that at least Spotify and Netflix uses some other container runtime than Docker on their production servers.

For a long time Docker was helpful and opened exposed ports on the firewall. So you wanted to access your redis ports locally and exposed it on the container? Now everything in there is accessible on the open internet.

I believe they've fixed it but I haven't used Docker in years so I wouldn't know.


I note the absence of a motivation.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: