3 ms·

As someone who did containers with LXC before docker, I think your characterization is off. The value in Docker isn't in the kernel features, but instead in the

As someone who did containers with LXC before docker, I think your characterization is off. The value in Docker isn't in the kernel features, but instead in the user space. Ever try Openshift 1/2, as painful as that was it was still better then rolling your own. Docker's big problem isn't what's below them, it's whats above them. Their monetizing strategy has to involve the fortune 500, and right now, all of the momentum in that area is being eaten by Google with Kubernetes. Kubernetes has a very vocal faction that wants nothing to do with Docker, and replace it with something else. Docker has plenty of challenges, but they have delivered significant value, most of which is still open source.

tyingq 9y ago
Your comment could be interpreted similarly. If the effort for k8s to move away from docker is minimal, that implies there wasn't much of anything novel in it.
- InTheArena 9y ago
  It’s not minimal. There is a incredible amount of effort going into this task.
squeed 9y ago
Indeed, especially as a company that has a reputation for producing unstable APIs that break between minor versions. This is a team that seems to think it is acceptable to return ASCII art and backspaces in their container management APIs: https://github.com/docker/swarm/issues/1214 https://github.com/docker/swarm/issues/1214 So, you're right, but they have a tainted reputation. I wish them all the best, but I don't have high hopes.
- rrdharan 9y ago
  I see the backspaces (as per that issue) but where's the ASCII art? EDIT: nevermind, found it via one of the linked issues: https://github.com/docker/swarm/issues/1237 https://github.com/docker/swarm/issues/1237
- shykes 9y ago
  > especially as a company that has a reputation for producing unstable APIs that break between minor versions. I wish people stopped repeating this without verifying it first. Here is a list of past breaking changes in the Docker API: https://docs.docker.com/engine/breaking_changes/ https://docs.docker.com/engine/breaking_changes/

tyingq 9y ago

Your comment could be interpreted similarly. If the effort for k8s to move away from docker is minimal, that implies there wasn't much of anything novel in it.

InTheArena 9y ago
It’s not minimal. There is a incredible amount of effort going into this task.

squeed 9y ago

Indeed, especially as a company that has a reputation for producing unstable APIs that break between minor versions. This is a team that seems to think it is acceptable to return ASCII art and backspaces in their container management APIs: https://github.com/docker/swarm/issues/1214 https://github.com/docker/swarm/issues/1214 So, you're right, but they have a tainted reputation. I wish them all the best, but I don't have high hopes.

rrdharan 9y ago
I see the backspaces (as per that issue) but where's the ASCII art? EDIT: nevermind, found it via one of the linked issues: https://github.com/docker/swarm/issues/1237 https://github.com/docker/swarm/issues/1237
shykes 9y ago
> especially as a company that has a reputation for producing unstable APIs that break between minor versions. I wish people stopped repeating this without verifying it first. Here is a list of past breaking changes in the Docker API: https://docs.docker.com/engine/breaking_changes/ https://docs.docker.com/engine/breaking_changes/