Repository navigation
Pin Buildx 0.37.1 for the Board's Compose build - #20
Merged
Merged
Conversation
Runner image ubuntu24/20261004.327 ships Buildx 0.37.2, whose bake now refuses ungranted entitlements under --progress=rawjson instead of skipping the consent check (GHSA-gwr2-q96m-6682). Compose grants fs.read only for build contexts, and the Dev Containers CLI 0.89.0 writes its generated Dockerfile outside the context, so every candidate's Dev Container build stopped with "additional privileges requested" before any check ran (devcontainers/cli#1320). No CLI release fixes it yet. The check action now installs Buildx 0.37.1 before devcontainers/ci and keeps the docker driver, so the build still runs on the runner's engine with its pulled workspace image. The job already runs the candidate's own code, so the consent check that 0.37.1 skips adds no protection here.
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.
The Drawing Board
contractcheck fails on every candidate before any check runs, for example firstdraft/drawing-board#79 and firstdraft/drawing-board#80:Runner image
ubuntu24/20261004.327ships Buildx 0.37.2. Its bake now refuses ungranted entitlements under--progress=rawjson(GHSA-gwr2-q96m-6682). Compose grantsfs.readonly for build contexts, and the Dev Containers CLI 0.89.0 writesDockerfile-with-featuresoutside the context. This is devcontainers/cli#1320, still open; 0.89.0 is the latest CLI release, so there is no fixed CLI to upgrade to. The last green Board run used the previous image,20260927.320; the upstream issue records Buildx 0.37.1 on that image.This change adds one step to
drawing-board/action.yml: the already-pinneddocker/setup-buildx-actionv4.3.0 installs Buildxv0.37.1with thedockerdriver. That driver creates no BuildKit container, so the build keeps using the runner's engine and its pulled workspace image. A comment cites the upstream issue so the pin can go once a CLI release fixes it.The image build and verify actions are unchanged; they run only on an approved image publication.
After this merges, Drawing Board's
ci.ymlpin moves from70e6d6dto the merged commit, as the maintainer guide asks.