3 ms·
This is especially complicated in an open source project like Docker. Docker seems to be locked between a rock and a hard place in that: a - They are post 1.0,
by timthelion 11y ago
This is especially complicated in an open source project like Docker. Docker seems to be locked between a rock and a hard place in that:
a - They are post 1.0, and there is an expectation that they won't break compatibility. This has meant a real slow down in development, and it is now very hard to get a pull request through.
b - Docker is totally imature and those pull requests are needed. It is lacking in basic functionality like the ability to mount and unmount volumes at run-time. It is also slow, and suffers from a codebase that was thrown together practially overnight. So it would actually be best if Docker Inc. went back to breaking things and getting things done.
Unfortunately, what seems to be happening is that Docker is failing to not break things and at the same time they are still paralized.
For subuser, there is yet a third problem. And that is that Docker is Docker Inc. And subuser being free software, it's not a nice feeling to know that my project is at the mercy of a single company.