Repository navigation
Pull base images through Harbor and retry Docker Hub requests - #47
Merged
Merged
Conversation
On 2026-11-05 all build runs failed with 429 Too Many Requests from Docker Hub, mostly on HEAD requests during push and in the merge job, once as "unauthenticated pull rate limit". The Docker Hub account is a Personal one, limited to 200 pulls in 6 hours. The build stages and COPY --from images that came from Docker Hub are now pulled through the Docker Hub proxy in Harbor (harbor.flownative.io/docker.io/...), so they no longer count against the pull rate limit of the Docker Hub account. The proxy can be read anonymously, so builds without credentials keep working. The merge job retries every imagetools call up to five times with a growing delay (30 s to 4 min), and only inspects the result in Harbor, which spares Docker Hub some requests. Refs OPS-8R Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All four build runs after the merge of the native arm64 builds failed with
429 Too Many Requestsfrom Docker Hub. Six of seven errors were HEAD requests (push, merge) with a bare 429, which the Docker documentation describes as the abuse rate limit. One was a GET in a merge job with "You have reached your unauthenticated pull rate limit". The Docker Hub account is a Personal one, limited to 200 pulls in 6 hours, and the builds, tests and test runs of that morning pulled roughly 150–200 times.golang,blackfire,composer) are pulled through the Docker Hub proxy in Harbor (harbor.flownative.io/docker.io/…). It serves the same digests and can be read anonymously, so builds without credentials (forks, local) keep working. Takes effect with the next release tag, because the workflow builds the code of the latest tag.docker buildx imagetoolscall is retried up to five times with a growing delay (30 s, 60 s, 120 s, 240 s). The result is inspected only in Harbor, no longer in Docker Hub.Tested:
actionlintis clean (apart from theubuntu-26.04labels it does not know yet). The merge step was run locally with a fakedockerthat fails twice and then succeeds, and with one that always fails. The changed Dockerfiles build locally through the proxy.Refs OPS-8R (https://minka.flownative.com/go/card/OPS-8R)