fix(provider): .110 trusts the registry mirror - #355
Merged
Conversation
rldyourmnd
enabled auto-merge
September 1, 2026 21:19
rldyourmnd
disabled auto-merge
September 1, 2026 21:20
The image's daemon.json has named https://192.0.2.1:5001 as a registry mirror since the docker image was first built, and zot on every member is configured as a docker.io pull-through cache. No worker ever trusted the certificate: the mirror's cert is signed by the fleet cache CA, the same CA the cache claim already hands the runner for the artifact store, and nothing installed it where dockerd looks. Every pull logged "x509: certificate signed by unknown authority" against the mirror and fell through to docker.io; the cache on gha-runner-1 held 30 MB after a month. The claim script now installs the CA at /etc/docker/certs.d/<mirror>/ca.crt for each mirror daemon.json names. dockerd reads that directory per request, so the mirror is real from the job's first pull, with no daemon restart and no image change. The mirror's certificate carries the bridge address as an IP SAN, so hostname verification holds. Claude-Session: https://claude.ai/code/session_0128syXKxAGCfJGRDxUUNQXp
Source ad6e658, built twice with CGO_ENABLED=0 go build -trimpath -buildvcs=false -ldflags "-buildid= -s -w -X main.version=v0.1.5-nddev.110 -X main.commit=<source>"; both builds agree on b2073169e22971d08a5c0255e4f0115941df0e8d4f51b89aa370177fc27339dc. Claude-Session: https://claude.ai/code/session_0128syXKxAGCfJGRDxUUNQXp
rldyourmnd
force-pushed
the
feat/provider-110-mirror-ca
branch
from
September 1, 2026 21:20
a21c7aa to
b7e4b64
Compare
rldyourmnd
enabled auto-merge
September 1, 2026 21:20
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
1 participant
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.
Provider v0.1.5-nddev.110. The image's daemon.json has named the member's zot as a docker.io pull-through mirror since the docker image was first built, and no worker ever trusted its certificate: every pull logged x509 unknown authority against the mirror and fell through to docker.io (30 MB cached after a month). The cache claim already hands the runner the fleet cache CA, which signs the mirror; the claim now installs it at /etc/docker/certs.d//ca.crt for each mirror daemon.json names. dockerd reads that directory per request, so the mirror is real from the first pull, with no daemon restart and no image change.
https://claude.ai/code/session_0128syXKxAGCfJGRDxUUNQXp