<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>user5994461</author><text>Original author from 5 years ago. Surprised to see this here 5 years later.&lt;p&gt;Docker really used to crash a lot back in the days, mostly due to buggy storage drivers. If you were on Debian or CentOS it&amp;#x27;s very likely that you experienced crashes (though a lot of developers didn&amp;#x27;t care or didn&amp;#x27;t understand the reasons the system went unresponsive).&lt;p&gt;There was notably a new version of Debian (with a newer kernel) published the year after my experience. It&amp;#x27;s a lot more stable now.&lt;p&gt;My experience is that by 2018-2019, Docker had mostly vanished as a buzzword, people were only talking about Kubernetes and looking for kubernetes experience.&lt;p&gt;edit: at that time Docker didn&amp;#x27;t have a way to clear images&amp;#x2F;containers, it was added after the article and follow up articles, I will never know if it was a coincidence but I like to think there is a link. I think writing the article was worth it if only for this reason.</text><parent_chain></parent_chain></comment><story><title>Docker in Production: A History of Failure (2016)</title><url>https://thehftguy.com/2016/11/01/docker-in-production-an-history-of-failure/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pbecotte</author><text>Even in 2016, I had been running production services in Docker successfully. Its interesting to me that they see the problem &amp;quot;Docker isn&amp;#x27;t designed to store data&amp;quot; without also seeing the solution &amp;quot;the docker copy-on-write filesystem isn&amp;#x27;t designed to be written to production- but volume mounts are&amp;quot;. I hadn&amp;#x27;t seen docker crashing hosts (still haven&amp;#x27;t) - but I&amp;#x27;m guessing that was caused by using the storage drivers.&lt;p&gt;The complaints about their development practices are valid (and haven&amp;#x27;t really improved), but even then the technology worked well so long as you understood its limitations.</text><parent_chain></parent_chain></comment><story><title>Docker in Production: A History of Failure (2016)</title><url>https://thehftguy.com/2016/11/01/docker-in-production-an-history-of-failure/</url></story>