Repository navigation
ci: postgres service image from the ECR Public mirror, pinned by digest - #450
Merged
Merged
Conversation
Docker Hub's anonymous pull limit stalled postgres-lineage. Same official image, same index digest on both registries (2026-10-10).
Member
Author
|
ork2 review @e550e129: OK (1 file, ci.yml).
|
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.
CI: postgres service image from the ECR Public mirror, pinned by digest
Why: the
postgres-lineagejob pulls itspostgres:16service image from Docker Hub and hits Docker Hub's anonymous pull limit; #449 is waiting on that check. This is the same fix as migrate#734 (web base image).Change:
.github/workflows/ci.yml, jobpostgres-lineage, servicepostgres:postgres:16→public.ecr.aws/docker/library/postgres:16@sha256:ca0bd484cb98bf4b24eb1010e73fb3fcbd6714d240fbc1a10eea5b7dbecb641d.A comment above it records the reason, the date and the digest. Nothing else changes.
Digest check (2026-10-10,
docker buildx imagetools inspect): both are an OCI image index (multi-arch, incl. linux/amd64), and the digests are identical:docker.io/library/postgres:16→sha256:ca0bd484cb98bf4b24eb1010e73fb3fcbd6714d240fbc1a10eea5b7dbecb641dpublic.ecr.aws/docker/library/postgres:16→sha256:ca0bd484cb98bf4b24eb1010e73fb3fcbd6714d240fbc1a10eea5b7dbecb641dOther Docker Hub pulls in this repo (not changed here; ORK decides the scope):
Dockerfile: threeFROM node:22-slimlines (deps,build,runtime).release.ymlbuilds this image on a release tag, so a release build can hit the same limit. Fix if needed: the same ECR digest migrate#734 pinned (node:22-slim@sha256:c3de60bf…).release.ymldocker/setup-buildx-action@v4pulls themoby/buildkitimage from Docker Hub by default (it can be pointed elsewhere withdriver-opts: image=…).ci.ymlhas no other service images.Proof:
docker pullof the pinned ref worked; the workflow YAML parses and names the new image.postgres-lineagegreen.