3 ms·

>You're the one who used Docker for a day or on nothing critical. Not really, but thanks for coming for me instead of offering any substance beyond hand waving

>You're the one who used Docker for a day or on nothing critical. Not really, but thanks for coming for me instead of offering any substance beyond hand waving. >Maybe you're also lucky to have started with Kubernetes, maybe even fully managed on Google Cloud. I mean, sure, I think it's crazy to try to use Docker in Prod without an orchestrator and don't think Swarm Mode is mature enough for such a use case. And no, I don't use GKE. Now that we've dropped anything that was really being discussed, let me agree with you, Docker itself is not my favorite, but that has nothing to do with containers or orchestrators in general and instead has to do with the QA of Docker and the frequency of breaks and regressions.

user5994461 9y ago
We both agree that orchestration is critical. Yet orchestrators are fairly new, the docker hype was strong long before they were viable, or existed at all. You'll forgive me but implying that one one should just use an orchestrator points to one ignoring their history -or lack thereof-. I have seen entire clusters taken out by a regression. Sadly, even the best orchestration cannot do much better than the core it is running on. You can google "docker in production" to get more substance.
- colemickens 9y ago
  >I have seen entire clusters taken out by a regression. I think we agree a lot actually :). Not sure Docker would call this one a regression, but... https://github.com/Azure/ACS/issues/3#issue-201986759 https://github.com/Azure/ACS/issues/3#issue-201986759 (that's me)