From e7abea95769de5ae700e502736176c8196cce093 Mon Sep 17 00:00:00 2001 From: Myasnikov Daniil Date: Mon, 22 Jun 2026 11:39:36 +0500 Subject: [PATCH] fix(ci): create buildx builder in the build step's DOCKER_CONFIG The "Set up Buildx" step in build-main.yaml ran without DOCKER_CONFIG, so docker/setup-buildx-action created the docker-container builder under the default ~/.docker. The build step runs with DOCKER_CONFIG=$RUNNER_TEMP/.docker (seeded before the builder existed and holding the OCIR auth), so it could not find the builder and failed immediately with `no builder "builder-" found`. The post-job `docker buildx rm` still succeeded because the action's cleanup runs under the default config where the builder actually lived. Set DOCKER_CONFIG on the Set up Buildx step so the builder instance is created in the same config the build step reads. Assisted-By: Claude Co-Authored-By: Claude Opus 4.8 (1M context) Signed-off-by: Myasnikov Daniil --- .github/workflows/build-main.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/.github/workflows/build-main.yaml b/.github/workflows/build-main.yaml index 97f4b59ff..927794676 100644 --- a/.github/workflows/build-main.yaml +++ b/.github/workflows/build-main.yaml @@ -74,6 +74,13 @@ jobs: uses: docker/setup-buildx-action@v3 with: driver: docker-container + env: + # buildx stores builder instances under $DOCKER_CONFIG/buildx/instances/. + # Create the builder in the SAME config the build step reads + # (runner.temp/.docker, seeded above and holding the OCIR auth); without + # this the builder lands in the default ~/.docker and the build step fails + # with `no builder "" found`. + DOCKER_CONFIG: ${{ runner.temp }}/.docker - name: Build all images and write mode=max cache run: make build