我似乎没有得到它.
也许这只是一个新方向.
希望有人能解释Docker vs Rocket的根本利弊.
谢谢
https://coreos.com/blog/rocket/
https://github.com/coreos/rocket
解决方法
CoreOS以及others开放源代码开发商和初创公司都表示,Docker打破了“标准容器”的概念,简洁性和可组合性,而started from则由removed original shipping containers ‘manifesto’证实.
在我身边,我已经看到许多信号,从Docker品牌的“法律授权”开始,到LXC containers年底,Docker基地的Linux开源技术从一开始就允许自己爬升.对我们第一个热烈的反应here,反映了所有Solo Hyakes(Docker项目的创始人和创始人)对CoreOS公告的“反击”.
那就是为什么我最近好奇(好笑地)最近宣布的所罗门铉：“We’re standing on the shoulders of giants”
他们也提出了对安全性和组合性观点的怀疑：
From a security and composability perspective,the Docker process
model – where everything runs through a central daemon – is
fundamentally flawed. To “fix” Docker would essentially mean a rewrite
of the project,while inheriting all the baggage of the existing
implementation.
那么火箭在最后呢？
Rocket is an alternative to the Docker runtime,designed for server
environments with the most rigorous security and production
requirements. Rocket is oriented around the App Container
specification,a new set of simple and open specifications for a
portable container format.
Docker有什么区别？
promise foundation of freedom and industrial open standards喜欢在DNS,HTTP,IMAP,SMTP,TCP / IP,ISO / OSI堆栈…互联网？或者更具体的安全性和可组合性.
看看折衷演讲者和惊人的developer凯尔西Hightower Rocket Tutorial & Demo.
正在进行的更新(SPECs – OPENSOURCE – VISION)：
[MUST READ] Amazing nitty-gritty details about the matter of Docker flawed
universal toolkit for emulating Heroku,regardless of stack or container engine
