build: migrate base-image mirror to anonymous-pull fluidmirror (eastus2)#27496
Merged
ChumpChief merged 2 commits intoJun 5, 2026
Merged
Conversation
… mirror ACR The public mirror ACR now allows anonymous pull, so the per-pipeline 'Fluid Public Mirror Container Registry' service-connection auth is no longer needed for base-image pulls. This also restores cross-fork PR compatibility for the server-* pipelines (cross-fork PRs are blocked from accessing service-connection secrets, which silently caused the Docker build step to fall back to anonymous pull and 401 against the previously-locked-down ACR). The push-side service connection (`$(containerRegistryConnection)`) is still required when pushing built images in the internal project. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Migrates the server-* base-image mirror from fluidpublicmirror (westus2, auth'd pull) to fluidmirror (eastus2, anonymous pull). Co-locating the ACR with the 1ES build pools (also in eastus2) makes legitimate CI egress free same-region transfer; a Cost Management budget on the new RG provides an abuse tripwire. AB#74558 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Hi! Thank you for opening this PR. Want me to review it? Based on the diff (26 lines, 2 files), I've queued these reviewers:
How this works
|
Contributor
Fleet Review — CleanNo issues found across the reviewer fleet for this run. |
Contributor
|
🔗 No broken links found! ✅ Your attention to detail is admirable. linkcheck output |
Abe27342
approved these changes
Jun 5, 2026
alexvy86
approved these changes
Jun 5, 2026
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.
Description
Switches the
server-*base-image mirror fromfluidpublicmirror(westus2, AcrPullservice connections) to a new ACR
fluidmirror(eastus2, anonymous pull). This:server-*pipelines. Cross-fork PRs areblocked from accessing service-connection secrets, which silently caused the Docker
build step to fall back to anonymous pull and 401 against the previously-locked-down
ACR. PR chore(server-gitssh): bump base image to alpine 3.23.4 #27445 (and any future server-* PR from a fork) will pass CI again.
'Fluid Public Mirror Container Registry'service-connectionwiring from
templates/build-docker-service.yml. The push-side service connection(
$(containerRegistryConnection)) is unchanged.egress is free same-region transfer instead of westus2-to-eastus2 cross-region. A
Cost Management budget on the new resource group provides an abuse tripwire.
Operational details (anonymous-pull approval from OpSec, ACR config, Cost Management
budget) are tracked in AB#74558. No Dockerfile changes — base-image digest pins are
preserved byte-for-byte in the new mirror.
The old
fluidpublicmirrorACR will be torn down in a follow-up after this soaks onmain.Reviewer Guidance
The review process is outlined on this wiki page.
End-to-end verification is the
server-*pipeline runs on this PR — they exercisethe exact same Docker build step that's been failing under network isolation.