Skip to content

Commit e7abea9

Browse files
myasnikovdaniilclaude
myasnikovdaniil
and
claude
committed
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-<uuid>" 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 <[email protected]> Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]> Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent aeaedca commit e7abea9

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

‎.github/workflows/build-main.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,13 @@ jobs:
7474
uses: docker/setup-buildx-action@v3
7575
with:
7676
driver: docker-container
77+
env:
78+
# buildx stores builder instances under $DOCKER_CONFIG/buildx/instances/.
79+
# Create the builder in the SAME config the build step reads
80+
# (runner.temp/.docker, seeded above and holding the OCIR auth); without
81+
# this the builder lands in the default ~/.docker and the build step fails
82+
# with `no builder "<name>" found`.
83+
DOCKER_CONFIG: ${{ runner.temp }}/.docker
7784

7885
- name: Build all images and write mode=max cache
7986
run: make build

0 commit comments

Comments
 (0)