[SEJeff]

Stuff like this (from Docker Inc, not Kubernetes) is why I'm really glad that Kubernetes is doing this.

I'm a Mesos user and absolutely can't wait until the Unified Containerizer bits are finished. The plan is to be able to pull down a docker image and run it as though it was being ran via the docker daemon, but not using docker and instead using the mesos native namespacing and control group bits. I would have already been a Kubernetes user had it not have depended on docker so heavily.

In our mesos environment, the only part we have issues with on a regular basis is docker. First it was the userland proxy and the performance and latency issues it introduced. Then it was the unresolved bug of docker just simply hanging under any sort of load[1] with upstream not really caring at all. Then there are random and difficult to reproduce issues where containers with bridged networking simply stop passing traffic from external interfaces into the containers when nothing has changed etc. So we use docker containers for some things, but try to limit them due to docker simply not being amazing for running production services for some of our use cases.

[1] https://github.com/docker/docker/issues/13885

[crb]

> I would have already been a Kubernetes user had it not have depended on docker so heavily.

You can use Kubernetes with rkt instead of Docker: https://github.com/kubernetes/kubernetes/tree/master/docs/ge...