Comment 2 for bug 1960858

A solution on the ROCKs end would be using an internal registry which could be used by launchpad (and possibly only by launchpad) to fetch the images from it instead of using third party registries (the built images would need to be pushed there as well).

From a launchpad perspective - until there is an internal registry available - we could authenticate to ECR prior the build step and perform builds from the images in there instead of using DockerHub. With a 10 image pulls/second rate we could perform 2 simultaneous builds at any given time. While we may still experience breakage with this approach (when more than 2 builds try to pull images for all architectures within the same second), a re-trigger would be enough to perform the next build.

With dockerhub's current 100 pulls/6 hour rates, we can only build 25 images every 6 hours, which is no longer enough for mass rebuilds on all the ROCKs we maintain.

So, should this bug be a request for ECR authenticated pulls instead?

On a side note, this issue also blocks us from using automated daily re-builds of the OCI images. Moving to pulling from ECR would not help if all the builds would be triggered at the exact same time everyday though.

[1] https://docs.aws.amazon.com/AmazonECR/latest/public/public-service-quotas.html