Talk of a Split from Docker

Re:Talk of a Split from Docker by hosh on Tuesday August 30, 2016 @11:19AM (#12390920)

As the proverb goes, "Choose, or someone will choose for you."

rkt is getting into Kubernetes as an alternative runtime engine:

http://thenewstack.io/kubernetes-chief-we-back-docker-althou... (2015)

http://blog.kubernetes.io/2016/07/rktnetes-brings-rkt-contai... (2016)

Back then it was, "It's sad to see so much drama; Docker engine has much more traction." Remember all of that?

The story is now, "hey, rkt lets us test out our framework for supporting alternative runtime engine".

There's a shifting attitude there. Goodwill from the community is eroding. I don't know how long this window will remain open, but it won't remain open indefinitely.

[ Parent | on HN ]

Re:Talk of a Split from Docker by amouat on Tuesday August 30, 2016 @11:26AM (#12390992)

I think there's also momentum to add runc as an alternative runtime engine, which makes sense.

Also, Mesos have started shipping their own container runtime.

This feels like an inflection point in the history of containers.

[ Parent | on HN ]

Re:Talk of a Split from Docker by cyphar on Tuesday August 30, 2016 @11:50AM (#12391198)

> I think there's also momentum to add runc as an alternative runtime engine, which makes sense.

Actually, we're working on getting generic OCI runtimes supported (runC being an example of such a runtime). In principle, you should be able to swap out the OCI runtime and still get Kubernetes to work with that runtime. It's an exciting time. :D

[ Parent | on HN ]