3 ms·
I don't know about rest of you but at our company we went through a lot of pain dealing with CoreOS. If we had known sooner, I'd gladly have taken a minimal Ubu
by jaequery 12y ago
I don't know about rest of you but at our company we went through a lot of pain dealing with CoreOS. If we had known sooner, I'd gladly have taken a minimal Ubuntu to run Docker over CoreOS. For one, requiring reboot to update is astrocious!
Because of these experiences, I just don't much faith in CoreOS guys (at least not yet), and the standard they are creating I think kills the best aspect of Docker, the freedom!
And regards to @shykes response, he was right on all points. Who in their right mind would adopt a supposed "Standard" written only 3 days ago? Doesn't matter who wrote it, it is just very unreasonable to accept a Standard without putting it through the test of time. This is a Standard, once in place you can't really change later, so aren't you glad that they didn't just jump on things?
Also, if you are in Docker's position, why would you want to risk limiting yourself to a single standard? Things change, fads change, people come up with better ideas, etc... No one knows. Some may want a much simpler spec (I for one), others may want something more thorough and detailed, etc. Just let the people decide the standard and let it run it's course, eventually the best will come out on top.
- avtar 12y agoat our company we went through a lot of pain dealing with CoreOS. If we had known sooner, I'd gladly have taken a minimal Ubuntu to run Docker over CoreOS. For one, requiring reboot to update is astrocious! As someone who hasn't invested a lot of time in evaluating CoreOS yet I would be interested in hearing about what other pain points you encountered. The reboot to update requirement seems straightforward given what they state in their documentation https://coreos.com/using-coreos/updates/ https://coreos.com/using-coreos/updates/