Skip to content

fix: use ECR pull-through cache for Docker Hub base images - #15

Closed
dhaley wants to merge 1 commit into
developfrom
fix/dockerfile-ecr-pull-through-cache
Closed

dhaley wants to merge 1 commit into
developfrom
fix/dockerfile-ecr-pull-through-cache

Conversation

@dhaley

@dhaley dhaley commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

When ROCKER_REGISTRY build arg is set (e.g. to an ECR pull-through cache prefix like 991404956194.dkr.ecr.us-west-2.amazonaws.com/docker-hub), Docker Hub images are pulled via the ECR cache. This avoids Docker Hub rate limits and transient 502 errors that break CI builds.

When ROCKER_REGISTRY is unset (local dev), falls back to pulling directly from Docker Hub.

The CodeBuild project already passes ROCKER_REGISTRY as a build arg (configured in the doeseed-seedweb terraform).

When ROCKER_REGISTRY is set (e.g. to the ECR pull-through cache prefix),
Docker Hub images are pulled via the cache, avoiding rate limits and
transient Docker Hub outages.

When ROCKER_REGISTRY is unset (local dev), falls back to pulling
directly from Docker Hub.
@dhaley dhaley closed this Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant