4 ms·
I don't use Docker so I don't know how opinionated this issue is, but it paints a bleak picture of the project. Breaking stuff after the 1.0 release should gen
by Ianvdl 11y ago
I don't use Docker so I don't know how opinionated this issue is, but it paints a bleak picture of the project.
Breaking stuff after the 1.0 release should generally be reserved for major versions (i.e. 1.0 -> 2.0), and incorrect basic documentation and specs are embarrassing for a project of this size.
Is this just a case where the project has been adopted too soon and developed too fast? It seems like Docker still has maturity issues past version 1.0 (based on a number of other negative responses to the project I've read elsewhere as well).
- dimgl 11y agoI can clue you in: it's extremely opinionated. After 1.0 there haven't been huge breaking changes.
- timthelion 11y agoI wrote a list of things that off the top of my head had broken things. Each of those changes meant that subuser couldn't run at all.
- toomuchtodo 11y agoDevOps/Infrastructure guy here at a startup that uses Docker in production. Docker has consistently broken in point releases after 1.0. "Why yes, I'd absolutely love to use your immature containerization ecosystem to manage mission critical infrastructure". To be fair, it was my mistake for not pushing back hard against Docker. Lesson learned.