Skip to content

feat(image): bake the CodeQL bundle and point dockerd at the member mirror - #323

Merged
rldyourmnd merged 1 commit into
mainfrom
feat/codeql-in-the-tool-cache-and-a-docker-mirror
Aug 31, 2026
Merged

feat(image): bake the CodeQL bundle and point dockerd at the member mirror#323
rldyourmnd merged 1 commit into
mainfrom
feat/codeql-in-the-tool-cache-and-a-docker-mirror

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

Kills two measured per-job taxes: the 800 MB CodeQL bundle download on every analyze job (now a pinned tool-cache toolchain, upstream checksum, smoke-verified as the runner) and direct Docker Hub pulls from one shared egress address (dockerd mirrors via the member zot at 192.0.2.1:5001 with safe upstream fallback until the zot sync surface ships). Aliases b21/b14.

https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF

…irror

Two measured per-job taxes leave the images:

- Every analyze job on an ephemeral runner downloaded the 800 MB CodeQL
  bundle. The action resolves the runner tool cache first --
  CodeQL/0.0.0-codeql-bundle-v<ver>/ with the x64.complete marker -- so the
  bundle is now a pinned toolchain like go or uv, verified by upstream
  checksum at build and by `codeql version` as the runner in both smokes.
- Every docker pull went straight to Docker Hub: one shared egress address
  against a 100-pulls-per-6h anonymous limit, full layers on every
  disposable worker. dockerd on the docker family now names the member zot
  (https://192.0.2.1:5001) as its registry mirror. dockerd falls back to the
  upstream on mirror miss or refusal, so the line is safe before the zot
  sync surface is deployed and instant once it is.

The network-surface inventory classifies docker-provision.sh now that it
carries a URL. Aliases move to b21/b14 (VM manifests follow to b18/b17).

Claude-Session: https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF
@rldyourmnd
rldyourmnd merged commit 4fcefa1 into main Aug 31, 2026
10 checks passed
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