News for hackers. Stuff that matters.

A comment on Talk of a Split from Docker. Parent comment

Re:Talk of a Split from Docker by philips on Tuesday August 30, 2016 @12:06PM (#12391338)
We (CoreOS) built rkt because we feel strongly that the container engine should be a stable and fundamental building block of software. By itself rkt is not a product and we want to ensure it is something that can be integrated into other systems. For example, we continue to add rkt support to Kubernetes[1] to provide a user transparent option for container engines. Similarly, there are integrations with Mesos and others.

Also, rkt has had significant external contribution like the virtual machine isolation work from Intel[2]. We have spun out independent projects like the Container Networking Interface (CNI)[3] that is now used in Kubernetes, Cloud Foundry, and Mesos.

Stable and robust components are necessary to make this ecosystem work for people operating them. And we built rkt to help the entire ecosystem (and yes ourselves) be successful with that. The product strategy ends there. If a community of folks felt putting rkt into an independently managed foundation would help achieve that goal we would be happy to do that work with others.

But, I think the project has a good track record of working with others and focusing on a narrow feature set.

[1] http://blog.kubernetes.io/2016/07/rktnetes-brings-rkt-contai... [2] https://coreos.com/blog/rkt-0.8-with-new-vm-support/ [3] https://github.com/containernetworking/cni

[ Parent | on HN ]
Re:Talk of a Split from Docker by raesene9 on Tuesday August 30, 2016 @02:16PM (#12392490)
Out of curiousity, where do you feel that Docker has less of a focus on stability than rkt, is it just in releasing swarm or in other areas?

Whilst I'm more familiar with Docker than rkt it seems that both projects are still changing quite quickly and have a lot of movement in terms of features being added & changed...

[ Parent | on HN ]
Re:Talk of a Split from Docker by philips on Tuesday August 30, 2016 @03:36PM (#12393193)
rkt tries to stay out of the way for everything that isn't "download, validate, and execute a container". For example, it doesn't know about networks but will hook out to CNI to setup a network namespace. It isn't an init system and will instead rely on a system init system to monitor it. It doesn't do any clustering but can be used by things like Kubernetes.
[ Parent | on HN ]