kraken

1) You can run your own pull-through cache[0] 2) You can use a different registry 3) Run something like kraken[1] so machines can share already-downloaded images with eachother 4) If you need an emergency response, you can docker save[2] an image on a box that has it cached and manually distribute it/load it into other boxes 0: https://docs.docker.com/registry/recipes/mirror/ 1: https://github.com/uber/kraken 2: https://docs.docker.com/engine/reference/commandline/save/

> Crosby explained that a registry would still be needed to handle the naming of images, but the content address blobs could be transferred from one machine to another without the need to directly interact with the registry. In the P2P model for image delivery, a registry could send a container image to one node, and then users could share and distribute images using something like BitTorrent sync. I believe this is the basic concept of Uber's Kraken project: https://github.com/uber/kraken I think it's a really clever idea, but I can also predict that a lot of enterprise companies will hear "bittorrent" and nope their way out of it.

Kraken was already taken[0] [0] https://github.com/uber/kraken

Kraken's readme included comparison with Dragonfly: https://github.com/uber/kraken#comparison-with-other-project...