Earlier quoted context omitted.
> That's a neat idea but probably unworkable in practice. Container images need to be reliably available quickly; there is no appetite for the uncertainties surrounding the average torrent download Bittorrent seems to work quite well for linux isos, which are about the same size as containers, for obvious reasons. IMO, the big difference is that, with bittorrent, it's possible to very inexpensively add lots of semi-r…
Nobody is going to accept worrying about whether the torrent has enough people seeding in the middle of a CI run. And your usual torrent download is an explicit action with an explicit client, how are people going to seed these images and why would they? And what about the long tail?
the .torrent file format, and clients, include explicit support for HTTP mirrors serving the same files that's distributed via P2P.