GitHub-hosted runners keep getting 429 Too Many Requests from Docker Hub (inbuxa-webmail and ihasvpn CI failed on it repeatedly on 2026-10-09). This pulls the same images through Google's Docker Hub mirror, mirror.gcr.io, before the next release build runs into it.
The image build is long, so locally: every new reference resolves on the mirror (docker buildx imagetools inspect; cargo-chef by its pinned digest), and the fork checks pass.
GitHub-hosted runners keep getting **429 Too Many Requests** from Docker Hub (inbuxa-webmail and ihasvpn CI failed on it repeatedly on 2026-10-09). This pulls the same images through Google's Docker Hub mirror, `mirror.gcr.io`, before the next release build runs into it.
The image build is long, so locally: every new reference resolves on the mirror (`docker buildx imagetools inspect`; cargo-chef by its pinned digest), and the fork checks pass.
GitHub's shared runners keep hitting Docker Hub's anonymous pull limit
(429), which fails docker builds there; inbuxa-webmail and ihasvpn hit
it on 2026-10-09. mirror.gcr.io serves the same images without that
limit (references checked on 2026-10-09; pinned digests unchanged).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
GitHub-hosted runners keep getting 429 Too Many Requests from Docker Hub (inbuxa-webmail and ihasvpn CI failed on it repeatedly on 2026-10-09). This pulls the same images through Google's Docker Hub mirror,
mirror.gcr.io, before the next release build runs into it.The image build is long, so locally: every new reference resolves on the mirror (
docker buildx imagetools inspect; cargo-chef by its pinned digest), and the fork checks pass.