Repository navigation
ci: pull base images from Amazon ECR Public instead of Docker Hub - #1720
Closed
brendan-kellam wants to merge 3 commits into
Closed
brendan-kellam wants to merge 3 commits into
brendan-kellam wants to merge 3 commits into
Conversation
Docker Hub token requests from GitHub-hosted runners are failing (auth.docker.io timeouts / 504s, falling back to the anonymous 429 limit), blocking release builds. Switch the Dockerfile base images and the Prisma migration check's Postgres image to Docker's official mirrors on public.ecr.aws/docker/library, which use the same images without depending on Docker Hub. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review. WalkthroughThe migration-check action and Docker build stages now use public Amazon ECR Docker Library image references. The image tags remain unchanged. ChangesContainer image registry references
Priority: ⬆️ High Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The registry changes preserve the expected PostgreSQL, Node, and Go images, and all three tags are publicly pullable for the supported build platforms. No blocking impact is indicated, so the PR is mergeable. Pre-merge checks |
 |
| Check name | Status | Explanation |
|---|---|---|
| Description Check |  |
Check skipped - CodeRabbit’s high-level summary is enabled. |
| Title check | |
The title clearly and concisely describes the main change: replacing Docker Hub base-image references with Amazon ECR Public references in CI and the Dockerfile. |
| Docstring Coverage | |
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0… |
| Linked Issues check | |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
✨ Finishing Touches
🧪 Generate unit tests (beta)
- Commit to this branch
- Create a new PR
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
@brendan-kellam your pull request is missing a changelog! |
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
1 participant
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.
Why
Since ~20:50 UTC on 2026-10-09, Docker Hub pulls from GitHub-hosted runners have been failing. Runners normally pull with a GitHub-provided Docker Hub credential (
account=githubactions) that exempts them from rate limits, butauth.docker.iois timing out / returning 504, so pulls either fail outright or fall back to anonymous and hit thetoomanyrequestslimit. This blocked the production release (run) in the Prisma migration check, and the image build pulls its base images from Docker Hub too. Many other projects are reporting the same thing (e.g. cleat-team/cleat#3290, openzigs/metis#1028).What
Pull Docker Official Images from Docker's mirror on Amazon ECR Public (
public.ecr.aws/docker/library/...). These are the same images, published by Docker, served without Docker Hub's auth service or rate limits.Dockerfile:node:24-alpine3.23andgolang:1.26-alpinebase images.github/actions/check-prisma-migrations/action.yml:postgres:16Verified all three tags exist on ECR Public.
🤖 Generated with Claude Code
Note
Low Risk
Registry-only renames for the same official image tags; no application, auth, or runtime logic changes.
Overview
Switches CI and image builds off Docker Hub by pointing three official image pulls at Amazon ECR Public (
public.ecr.aws/docker/library/...), which mirrors Docker Official Images without Docker Hub auth or rate limits.The Prisma migration check now starts Postgres with
public.ecr.aws/docker/library/postgres:16instead ofpostgres:16. The rootDockerfileuses the same ECR paths for thenode:24-alpine3.23andgolang:1.26-alpinebuild stages. Image tags and behavior are unchanged; only the registry hostname changes.Reviewed by Cursor Bugbot for commit b8602c5. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit