Skip to content

ci(pipelines): route server base images through internal mirror#27346

Draft
ChumpChief wants to merge 1 commit into
mainfrom
test/server-pipelines-acr-mirror
Draft

ci(pipelines): route server base images through internal mirror#27346
ChumpChief wants to merge 1 commit into
mainfrom
test/server-pipelines-acr-mirror

Conversation

@ChumpChief
Copy link
Copy Markdown
Contributor

@ChumpChief ChumpChief commented May 19, 2026

Adds an overridable BASE_IMAGE_REGISTRY build arg to the four server-* Dockerfiles (gitssh, gitrest, historian, routerlicious), defaulting to docker.io for unchanged local/external behavior. Each server-* pipeline overrides the arg via additionalBuildArguments to pull the base image from the internal mirror, avoiding the 1ES network-isolation block on registry-1.docker.io.

Also adds tools/pipelines/README.md documenting how to upgrade or add mirrored base images going forward.

AB#73353

Add ARG BASE_IMAGE_REGISTRY=docker.io to the four server Dockerfiles and
have each server-* pipeline override it via additionalBuildArguments to
point at the internal mirror namespace. This makes the build resilient
against 1ES network isolation policies that block egress to
registry-1.docker.io, while keeping local and external-contributor builds
unchanged (they continue to pull from Docker Hub).

The internal mirror uses the namespace layout mirror/docker/library/<image>
so that overriding BASE_IMAGE_REGISTRY is the only change needed to swap
between upstream and mirror.

Adds tools/pipelines/README.md describing how to maintain mirrored base
images going forward.

AB#73353

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 19, 2026

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (159 lines, 11 files), I've queued these reviewers:

  • Correctness — logic errors, race conditions, lifecycle issues
  • Security — vulnerabilities, secret exposure, injection
  • API Compatibility — breaking changes, release tags, type design
  • Performance — algorithmic regressions, memory leaks
  • Testing — coverage gaps, hollow tests

How this works

  • Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

  • Tick Start review below to dispatch the review fleet.

  • After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

  • This comment updates as new commits land; your reviewer selections are preserved.

  • Start review

@ChumpChief ChumpChief force-pushed the test/server-pipelines-acr-mirror branch from 29484af to 5427c6c Compare May 19, 2026 23:10
@github-actions
Copy link
Copy Markdown
Contributor

🔗 No broken links found! ✅

Your attention to detail is admirable.

linkcheck output


> fluid-framework-docs-site@0.0.0 ci:check-links /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test "npm run serve -- --no-open" 3000 check-links

1: starting server using command "npm run serve -- --no-open"
and when url "[ 'http://127.0.0.1:3000' ]" is responding with HTTP status code 200
running tests using command "npm run check-links"


> fluid-framework-docs-site@0.0.0 serve
> docusaurus serve --no-open

[SUCCESS] Serving "build" directory at: http://localhost:3000/

> fluid-framework-docs-site@0.0.0 check-links
> linkcheck http://localhost:3000 --skip-file skipped-urls.txt

Crawling...

Stats:
  288859 links
    1925 destination URLs
    2175 URLs ignored
       0 warnings
       0 errors


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