ci: allow production.cloudfront.docker.com in harden-runner egress#2552
Merged
EyeCantCU merged 1 commit intoMay 29, 2026
Merged
Conversation
Docker Hub serves image blobs from a CDN, and sometimes uses CloudFront (production.cloudfront.docker.com) in addition to the Cloudflare endpoint already allowlisted. Docker changed this recently (see Docker Hub release notes, ~a week ago: https://docs.docker.com/docker-hub/release-notes/), which is why crane pulls of Docker Hub images (e.g. chainguard/static in the e2e xcover test) started failing harden-runner egress with: dial tcp: lookup production.cloudfront.docker.com ... i/o timeout Same CloudFront usage was observed in mono CI: https://github.com/chainguard-dev/mono/actions/runs/26589819417/job/78350661305#step:18:25 Add production.cloudfront.docker.com:443 to the egress allowlist in the Test packages (e2e) and release jobs, alongside the existing Cloudflare endpoint.
EyeCantCU
approved these changes
May 29, 2026
Member
|
Thanks for fixing! |
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
2 participants
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.
Docker Hub serves image blobs from a CDN, and sometimes uses CloudFront (production.cloudfront.docker.com) in addition to the Cloudflare endpoint already allowlisted. Docker changed this recently (see Docker Hub release notes, ~a week ago: https://docs.docker.com/docker-hub/release-notes/), which is why crane pulls of Docker Hub images (e.g. chainguard/static in the e2e xcover test) started failing harden-runner egress with:
dial tcp: lookup production.cloudfront.docker.com ... i/o timeout
Same CloudFront usage was observed in mono CI, and fixed here:
https://github.com/chainguard-dev/mono/pull/41186
Add production.cloudfront.docker.com:443 to the egress allowlist in the Test packages (e2e) and release jobs, alongside the existing Cloudflare endpoint.
Melange Pull Request Template
Functional Changes
Notes:
SCA Changes
Notes:
Linter
Notes: