This does sound promising. Though if it restricts one to hosts using systemd than I don¹t see much value in it over Docker. However no need to preclude it on choice of init process alone, plus it exercises the ContainerInfo structure some more. +1
From: Tim Chen <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Monday, December 1, 2014 at 2:10 PM To: dev <[email protected]>, "[email protected]" <[email protected]> Subject: Rocket Hi all, Per the announcement from CoreOS about Rocket (https://coreos.com/blog/rocket/) , it seems to be an exciting containerizer runtime that has composable isolation/components, better security and image specification/distribution. All of these design goals also fits very well into Mesos, where in Mesos we also have a pluggable isolators model and have been experiencing some pain points with our existing containerizers around image distribution and security as well. I'd like to propose to integrate Rocket into Mesos with a new Rocket containerizer, where I can see we can potentially integrate our existing isolators into Rocket runtime. Like to learn what you all think, Thanks!
smime.p7s
Description: S/MIME cryptographic signature
