Hi everyone, sorry about the outage (which appears to be now fixed). I don't know what caused it but I'm sure the Hub team will post a post-mortem soon.
My educated guess is that it has something to do with our recent move off of Dotcloud as part as the sale to Cloud Control [1]. In my experience, migrations always introduce unexpected moving parts which can lead to service disruption in spite of thorough preparation.
Note on the registry being "just a crud server". That's true, I suppose. But at very large scale everything gets harder to do reliably.
About decentralization: there is a major development thread underway to make images self-describing. Once that is implemented, the naming of images will be decorrelated from their method of delivery, there is already talk of a bittorrent and ipfs plugin :)
My educated guess is that it has something to do with our recent move off of Dotcloud as part as the sale to Cloud Control [1]. In my experience, migrations always introduce unexpected moving parts which can lead to service disruption in spite of thorough preparation.
Note on the registry being "just a crud server". That's true, I suppose. But at very large scale everything gets harder to do reliably.
About decentralization: there is a major development thread underway to make images self-describing. Once that is implemented, the naming of images will be decorrelated from their method of delivery, there is already talk of a bittorrent and ipfs plugin :)
[1] http://techcrunch.com/2014/08/04/docker-sells-dotcloud-to-cl...