What the developer wrote
Authored by will
ci: use buildx in ci
Using buildx is required to properly load the correct driver, for use
with registry caching. Neither build, nor BUILDKIT=1 currently do this
properly.
Use of `docker buildx build` is compatible with podman.
What changed, and why it matters
This commit changes the Bitcoin Core continuous integration (CI) script to use Docker's 'buildx' plugin instead of the older 'docker build' command with BuildKit enabled. It is a build-infrastructure tweak intended to make Docker image caching work correctly. There is no indication this change affects the Bitcoin software users run, handles money, keys, network messages, or introduces any security vulnerability.
No security action required. Treat as a normal CI maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch modifies ci/test/02_run_container.sh, replacing ‘DOCKER_BUILDKIT=1 docker build’ with ‘docker buildx build’. The commit message explains that buildx is needed to load the correct driver for registry caching, which the plain build command with BUILDKIT=1 does not do. This is a CI container-build tooling change only.
Changed components
ci/test/02_run_container.shInspect captured patch +3 / −1
diff --git a/ci/test/02_run_container.sh b/ci/test/02_run_container.sh
index 119ab2e8..b3553f7f 100755
--- a/ci/test/02_run_container.sh
+++ b/ci/test/02_run_container.sh
@@ -42,8 +42,10 @@ if [ -z "$DANGER_RUN_CI_ON_HOST" ]; then
DOCKER_BUILD_CACHE_ARG="--cache-from type=local,src=${DOCKER_BUILD_CACHE_OLD_DIR} --cache-to type=local,dest=${DOCKER_BUILD_CACHE_NEW_DIR},mode=max"
fi
+ # Use buildx unconditionally
+ # Using buildx is required to properly load the correct driver, for use with registry caching. Neither build, nor BUILDKIT=1 currently do this properly
# shellcheck disable=SC2086
- DOCKER_BUILDKIT=1 docker build \
+ docker buildx build \
--file "${BASE_READ_ONLY_DIR}/ci/test_imagefile" \
--build-arg "CI_IMAGE_NAME_TAG=${CI_IMAGE_NAME_TAG}" \
--build-arg "FILE_ENV=${FILE_ENV}" \
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.