4 ms·
Ah.... Hahah... Hahhahahahhahahahahahahahah. No. During the 1 year I ran CoreOS in production, updates were turned off, because they caused all sorts of issue
by hagbarddenstore 10y ago
Ah.... Hahah... Hahhahahahhahahahahahahahah.
No.
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.
- politician 10y agoYou 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. Turn off auto updates.