5 ms·

I wonder why CoreOS weren't in that meeting. They provide a ton of stuff that could be seen as a docker plugin (flannel being the most obvious imo)

nesquikr0x 12y ago
Maybe because they're going their own direction with containers now https://coreos.com/blog/rocket/ https://coreos.com/blog/rocket/ edit: and because they disagree with docker's direction. Potentially, CoreOS left themselves out of the conversation
- lclarkmichalek 12y ago
  Isn't their disagreeing just another reason to have them there? Their feud is not helping either side.
  - Alupis 12y ago
    There's a plethora of quotes and cliches about surrounding yourself with only like-minded individuals and being in an echo chamber. I do believe CoreOS is likely one of the largest (the largets?) adopter of Docker, and their entire platform is built around Docker. Even with Rocket, they've stated they have no immediate plans to make CoreOS incompatible with Docker.
Gigablah 12y ago
The relationship between CoreOS and Docker isn't exactly warm at the moment: https://github.com/docker/docker/issues/9538#issuecomment-65967102 https://github.com/docker/docker/issues/9538#issuecomment-65...
- lclarkmichalek 12y ago
  The hate seems to be mostly going one way.
  - fundies 12y ago
    I don't think hate is the right term. Same goes for "one way", since it's genuinely not clear to me which way that is.
    - Alupis 12y ago
      > unless the community starts calling out their BS ? not sure what shykes is implying here. > 3-day old unfinished spec Actually it's been in the git repo for 13 days, been public for 8 days, and has been getting developed since January 2014 (Docker is not even twice as old). > no working implementation Actually, Rocket is the implementation, ACI is the spec. > a controversial background How so? Because Docker disagrees with it so it's controversial? > sponsored by a small venture-backed company I think shykes is forgetting Docker just raised an excess of $40 million on a $400 million evaluation. > with questionable motives Again not sure what shykes implies here... Docker is a for-profit commercial vendor just the same. The language and inaccuracies in shykes comment on github are shocking to say the least. Seems rather uni-directional "mud slinging", as shykes has previously put it[1]... [1] https://news.ycombinator.com/item?id=8683705 https://news.ycombinator.com/item?id=8683705
      - mbreese 12y ago
        Well, all of that is just the public view (and was pretty knee-jerk at that). Who knows what either company really thinks of the other... CoreOS was just smart enough not to engage publicly.
qkrijger 12y ago
Maybe because CoreOS was not present at the conference ... There were also no CoreOS talks, and that had nothing to do with Rocket, since the talks have been selected long ago.
shykes 12y ago
CoreOS got a dedicated meeting the previous week. I pitched all this to them in person and seemed to get a cautiously optimistic response with agreement to follow-up soon. The next day, they announced rocket without warning. I'm happy to spend as much time as needed with everyone to build a great ecosystem together. But if someone is not interested, they're not interested. I can't force them.
- lclarkmichalek 12y ago
  Oo so that's why you're so pissed. ah well
  - shykes 12y ago
    Doesn't excuse my initial knee-jerk reaction... Anyway, let's move on and focus on building cool stuff now :)
weavenetwork 12y ago
this began as a chat between me and solomon, and I then invited everyone at dockercon who was implementing network/extension related stuff. this all happened over a few hours... so wasn't possible to invite folks to hop on a plane from SFO at that point.

nesquikr0x 12y ago

Maybe because they're going their own direction with containers now https://coreos.com/blog/rocket/ https://coreos.com/blog/rocket/ edit: and because they disagree with docker's direction. Potentially, CoreOS left themselves out of the conversation

lclarkmichalek 12y ago
Isn't their disagreeing just another reason to have them there? Their feud is not helping either side.
- Alupis 12y ago
  There's a plethora of quotes and cliches about surrounding yourself with only like-minded individuals and being in an echo chamber. I do believe CoreOS is likely one of the largest (the largets?) adopter of Docker, and their entire platform is built around Docker. Even with Rocket, they've stated they have no immediate plans to make CoreOS incompatible with Docker.

Gigablah 12y ago

The relationship between CoreOS and Docker isn't exactly warm at the moment: https://github.com/docker/docker/issues/9538#issuecomment-65967102 https://github.com/docker/docker/issues/9538#issuecomment-65...

lclarkmichalek 12y ago
The hate seems to be mostly going one way.
- fundies 12y ago
  I don't think hate is the right term. Same goes for "one way", since it's genuinely not clear to me which way that is.
  - Alupis 12y ago
    > unless the community starts calling out their BS ? not sure what shykes is implying here. > 3-day old unfinished spec Actually it's been in the git repo for 13 days, been public for 8 days, and has been getting developed since January 2014 (Docker is not even twice as old). > no working implementation Actually, Rocket is the implementation, ACI is the spec. > a controversial background How so? Because Docker disagrees with it so it's controversial? > sponsored by a small venture-backed company I think shykes is forgetting Docker just raised an excess of $40 million on a $400 million evaluation. > with questionable motives Again not sure what shykes implies here... Docker is a for-profit commercial vendor just the same. The language and inaccuracies in shykes comment on github are shocking to say the least. Seems rather uni-directional "mud slinging", as shykes has previously put it[1]... [1] https://news.ycombinator.com/item?id=8683705 https://news.ycombinator.com/item?id=8683705
    - mbreese 12y ago
      Well, all of that is just the public view (and was pretty knee-jerk at that). Who knows what either company really thinks of the other... CoreOS was just smart enough not to engage publicly.

qkrijger 12y ago

Maybe because CoreOS was not present at the conference ... There were also no CoreOS talks, and that had nothing to do with Rocket, since the talks have been selected long ago.

shykes 12y ago

CoreOS got a dedicated meeting the previous week. I pitched all this to them in person and seemed to get a cautiously optimistic response with agreement to follow-up soon. The next day, they announced rocket without warning. I'm happy to spend as much time as needed with everyone to build a great ecosystem together. But if someone is not interested, they're not interested. I can't force them.

lclarkmichalek 12y ago
Oo so that's why you're so pissed. ah well
- shykes 12y ago
  Doesn't excuse my initial knee-jerk reaction... Anyway, let's move on and focus on building cool stuff now :)

weavenetwork 12y ago

this began as a chat between me and solomon, and I then invited everyone at dockercon who was implementing network/extension related stuff. this all happened over a few hours... so wasn't possible to invite folks to hop on a plane from SFO at that point.