3 ms·

Is this specifically aimed at compute cloud users for faster deploys? I would much rather go with dockerhub than use this. Egress pricing sucks. I'd rather h

by tonyhb 12y ago

Is this specifically aimed at compute cloud users for faster deploys? I would much rather go with dockerhub than use this. Egress pricing sucks. I'd rather have it from docker, who made the tool for my containers, than google. What about docker 1.6, with image and container labels? Will Google keep this up to date?

hueving 12y ago
>I'd rather have it from docker, who made the tool for my containers, than google. Interesting take on things. It's mostly contributions from Google that made containers viable in the first place.
- tonyhb 12y ago
  True that, the original LXC library was Google. Then Docker wrote their own implementation called libcontainer (and systemd-nspawn popped about). While Google made containers possible I think Docker made them happen. I can't imagine committing an LXC container and pushing it to a repo if it weren't for docker. Nor would I want to manage raw networking in LXC. Nor sharing of filesystems.
  - justicezyx 12y ago
    Well, the world outside of Google discovered container, that's a more appropriate description. Google is a living endorsement to the paradigm. But Docker didnt make them happen, docker merely discovered it.
  - asuffield 12y ago
    (Tedious disclaimer: my opinion, not my employer's. Not representing anybody else. I work at Google, not on borg) You might find the borg paper very interesting: http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/43438.pdf http://static.googleusercontent.com/media/research.google.co... The bits of containers that made it out into lxc are essentially borglet features. The rest of the infrastructure around it was never released to the outside world, and now docker is recreating some of that infrastructure. We've had borg for a long time ;) There's lots more detail in the paper about how these pieces relate to each other.

by tonyhb 12y ago

hueving 12y ago

>I'd rather have it from docker, who made the tool for my containers, than google. Interesting take on things. It's mostly contributions from Google that made containers viable in the first place.

tonyhb 12y ago
True that, the original LXC library was Google. Then Docker wrote their own implementation called libcontainer (and systemd-nspawn popped about). While Google made containers possible I think Docker made them happen. I can't imagine committing an LXC container and pushing it to a repo if it weren't for docker. Nor would I want to manage raw networking in LXC. Nor sharing of filesystems.
- justicezyx 12y ago
  Well, the world outside of Google discovered container, that's a more appropriate description. Google is a living endorsement to the paradigm. But Docker didnt make them happen, docker merely discovered it.
- asuffield 12y ago
  (Tedious disclaimer: my opinion, not my employer's. Not representing anybody else. I work at Google, not on borg) You might find the borg paper very interesting: http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/43438.pdf http://static.googleusercontent.com/media/research.google.co... The bits of containers that made it out into lxc are essentially borglet features. The rest of the infrastructure around it was never released to the outside world, and now docker is recreating some of that infrastructure. We've had borg for a long time ;) There's lots more detail in the paper about how these pieces relate to each other.