Docker in Production: A History of Failure
Well, this person seems to have had a hard few months. I have a lot of problems with the post though:<p>- Docker do not own CoreOS and did not create the distro<p>- Docker did not write OverlayFS<p>- There are issues with storage drivers. Don&#x27;t use AUFS for the reasons outlined. I&#x27;ve had no issues with Overlay2, but note there is also devicemapper (which Red Hat have poured a lot of time into) and BTRFS. And ZFS now IIRC.<p>- It&#x27;s not correct to say Docker was designed &quot;not&quot; to do persistent data. You do need to be aware of what you&#x27;re doing, and I suggest not running DBs in containers until you have the solved the FS issues and have experience with orchestration.<p>- Kubernetes has been around for a while now and is fairly stable in my view. Swarm isn&#x27;t rubbish, but the new version is very young and you may run into issues in the short term.<p>- With microservices, when you are running lots of small containers, you have to expect them to crash now and again. It&#x27;s just the law of averages. You need to design your application to accept this and deal with it when it happens.<p>If you hit this many problems with any given tech, I would suggest you should be looking for outside help from someone that has experience in the area.