Repository navigation
fix(isolation): apply the configured registry to namespaced images - #1759
Merged
Dumbris merged 1 commit intoOct 26, 2026
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Dumbris
approved these changes
Oct 26, 2026
Dumbris
left a comment
Member
There was a problem hiding this comment.
Verified: the PR test fails on main for the reason described and passes on this branch merged with main; race tests for the touched packages and CI lint (bare and server tags) are clean. Also built and tested together with the rest of this batch, independently reviewed, and cross-reviewed with a second model.
Member
|
Merged. Thank you, @rudycelekli! |
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.
Bug
docker_isolation.registryis documented as the custom registry for isolation images, and air-gapped installs depend on it (seeisolation_git_image_registry_test.go).buildFullImageNametreats any image containing a/as already qualified and returns it unchanged. A Docker Hub namespaced image such asmyorg/node-mcp:1therefore bypasses the configured registry and is pulled from docker.io. The finalregistry + "/" + imagebranch is unreachable.Docker's own rule is that the first path component is a registry host only if it contains
.or:, or islocalhost. Otherwise it is a Docker Hub namespace.Trigger
A per-server
isolation.image: "myorg/node-mcp:1"triggers it too.mirror.corp/myorg/node-mcp:1.myorg/node-mcp:1, which a host without internet access cannot pull.Fix
Use Docker's host rule (
imageHasRegistryHost) to decide whether a reference is already qualified. With a custom registry configured, namespaced images get the registry prefix like official images already do. With no registry configured,org/imageis still returned unchanged, so ordinary installs see no difference. Fully qualified references (ghcr.io/...,localhost:5000/...,registry.local/...@sha256:...) are untouched.Test
TestBuildFullImageName_ConfiguredRegistryPrefixesNamespacedImagesis a table test covering the configured-registry and no-registry cases above.Commands run
CGO_ENABLED=0 go test -count=1 ./internal/upstream/core: ok (includes the existing git-image registry tests)git stashofisolation.go), the new test fails withbuildFullImageName("myorg/node-mcp:1") = "myorg/node-mcp:1", want "mirror.corp/myorg/node-mcp:1".gofmt -lon the edited files: no output