Repository navigation
fix(buildkitd): pin moby/buildkit v0.34.2 by digest (Brotli CVE-2026-111497) - #212
Merged
Merged
Conversation
Deploying batchivo with
|
| Latest commit: |
106c70f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://378ae88f.batchivo.pages.dev |
| Branch Preview URL: | https://fix-buildkitd-pin-v0-34-2.batchivo.pages.dev |
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.
Why
buildkitdused the floatingdockerhub-cache/moby/buildkit:latestwithimagePullPolicy: IfNotPresent, so node03 kept running an old cached pull (buildkit v0.32.2, Alpine 3.23.5, brotli-libs 1.2.0-r0, vulnerable to CVE-2026-111497) even though upstreamlatestwas fixed on 3 Nov.Already live
On 10 Nov (Jonathan approved the outstanding cluster updates) I pre-pulled the current
lateston node03 and rankubectl rollout restart deploy/buildkitdat 12:38:50 GMT (ready 12:39:03, no build running at the time). The pod now runsmoby/buildkit@sha256:c5f8862f…= v0.34.2, Alpine 3.23.7, brotli-libs 1.2.1-r0. The image field was not changed, so Argo CD stayed Synced.This PR
Pins the same image by tag + digest (
v0.34.2@sha256:c5f8862f…, the same as upstreamlatesttoday), like the umami/cloudflared/github-runner pins, so a future restart can't fall back to a stale cache.Merging makes Argo CD (batchivo-app, self-heal) restart buildkitd once on the same image (Recreate, about 15 s). Best merged when no Woodpecker build is running.
Verified
buildctl debug workersOK; a test Dockerfile build (busybox base, RUN step, local export) succeeded on the new daemon.