[sentiental]

I have been concerned that Docker's scope was expanding too far for a while now, so I'm glad to see an alternative that might work appear on the horizon. That said, I am somewhat concerned that CoreOS has a suspiciously similar business model to where Docker would probably like to be.

It's in a business's best interest, and exceedingly common practice, to "land and expand" with something clear and compelling, and following that add features to compete with alternative solutions. I don't think there's anything inherently altruistic about CoreOS that would keep Rocket lean in the long-run, especially as they begin migrating their various tools away from Docker containers.

[rafikk]

I had the same initial reaction, but I think there's good reason to trust the CoreOS folks to remain faithful to the project's goals. Containerization (although foundational) is one part of CoreOS's platform. It's easy to see where the boundaries fall, e.g. I expect systemd and fleetd to keep their respective functionality and not overlap with Rocket.

It become pretty clear once dotCloud became Docker Inc. that they intended to capitalize on the "Docker" brand to sell an integrated orchestration platform. CoreOS already has enterprise customers for their operating system and related components. They seem like the perfect team to take this challenge on.

[Alupis]

I think it's also crucial users have more than one viable container option.

[jmendeth]

The difference here would be, IMO, that they have clearly made openness one of Rocket's goals: the formats should be well-specified and maintained separately so that other implementations can run them.

[altcognito]

> I have been concerned that Docker's scope was expanding too far for a while now

What features were recently introduced that it increased Docker's scope?

[lclarkmichalek]

Talk of Docker cluster, which might include a network overlay layer a la weave

[shykes]

All of which will be fully pluggable with a "batteries included but removable" design, just like we did with sandboxing and storage.

[lclarkmichalek]

You may need to make that clearer to some of the people that are due to be building your plugins: reading http://weaveblog.com/2014/11/13/life-and-docker-networking/, I get the feeling that they're not thrilled about it.

[shykes]

maybe they're busy designing the interface and implementing a proof-of-concept with us as we speak, instead of blogging and twittering.

[lclarkmichalek]

Welp, I'm putting "been snarked by founder of Docker" on my CV.

[wmf]

They'll probably keep Rocket lean and introduce new features as "separate projects" that will all be bundled into CoreOS.