The docker hub rate limits continue to pester us (though many of the mitigations we have already employed seem to be helping). One thing we haven't done is to force connectivity to the docker hub registry via ipv4 when building images. This should help because docker hub treats ipv6 /64 blocks as a single entity for rate limiting purposes but ipv4 addrs are individually tracked. Change-Id: Ia108e6fd6c19727083ae4b3b07c45d3503b5fe89
740 B
740 B