I've read this article about CoreOS's new container runtime, rkt, and I'm curious about this section:

Why not just fork Docker?

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.

As a security newbie, could someone enlighten me about the meaning of this paragraph?

  • 2
    You have to consider that Docker development ... somewhat deviates ... from the normal open-source model. This is also called "a battle of architects". – Deer Hunter Aug 31 '15 at 15:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.