Subject: [Tools-discuss] Upcoming disruptive changes to Docker Hub and CI services

From: "Martin Thomson" <[email-masked]>
Date: Tue, 06 Oct 2020 11:55:31 +1100

For those people using Circle or Travis for continuous integration of their drafts, a change to the way that Docker Hub authorizes access to docker images will likely break all continuous integration builds.

https://docs.docker.com/docker-hub/download-rate-limit/ and https://www.docker.com/blog/scaling-docker-to-serve-millions-more-developers-network-egress/ explain that limits will be applied to client IP ranges, which obviously leads to CI services being adversely affected.

This will likely break any flow that doesn't use GitHub Actions.  GitHub use their own image repository so are unaffected.

Circle have provided this information: https://circleci.com/docs/2.0/private-images/  Anyone looking to avoid this rate limiting will (likely) need to make some manual changes to their .circleci/config.yml file and build configuration.  I'm not currently aware of any way to avoid this extra configuration step.  Any ideas for how this might be automated or how automation might help would be appreciated.