The next question that needs to be answered at CoreOS: "Why, exactly, are we maintaining our own Linux distro when the Go binaries that we're writing can mostly ignore userspace?"
During the 1 year I ran CoreOS in production, updates were turned off, because they caused all sorts of issues.
They only reliable way of doing updates in CoreOS is to replace the machine and reconfiguring it. But then you need to automate joining etcd, which itself is a major pain in the ass.
You don't deserve the downvotes. When Docker arbitrarily changes something important and pushes those changes to Docker Hub, CoreOS is dragged along for the ride.
We had our auto-updating servers move to Docker 1.10 over a weekend. Of course, this brought down our CI/CD process because that version of Docker changed something important. Our staging environment was totally horked, but our production environment survived due to an unexplained reboot lock. We were lucky.
There were Linux distros that could upgrade across releases twenty(!) years ago. There is so much opportunity in infrastructure right now, so it strikes me as weird that CoreOS took a bunch of VC money to go off on an extended Linux-From-Scratch-Adventure.
