From beceeb4c1fe77180fe11bfc2c5dbada8d31a1a6e Mon Sep 17 00:00:00 2001 From: X9 Dev Date: Fri, 29 May 2026 17:55:50 +0200 Subject: [PATCH] ci(runner): bind-mount docker socket via container.options docker_host auto-mount did not expose the socket on runner 6.3.1; mount it explicitly so the deploy.json step's docker exec works. Co-Authored-By: Claude Opus 4.8 --- runner-config.yml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/runner-config.yml b/runner-config.yml index 9a7ef2f..51e913f 100644 --- a/runner-config.yml +++ b/runner-config.yml @@ -17,7 +17,10 @@ container: privileged: false valid_volumes: - '**' - # Auto-detect and mount the host docker socket into job containers so steps - # like "Update deploy.json" can `docker exec xetup-web`. ("-" disabled it.) - docker_host: "" + # Explicitly bind-mount the host docker socket into job containers so steps + # like "Update deploy.json" can `docker exec xetup-web`. docker_host auto-mount + # ("") did not work on runner 6.3.1, so we mount the socket via options and + # let the job's default DOCKER_HOST (unix:///var/run/docker.sock) pick it up. + docker_host: "-" + options: "-v /var/run/docker.sock:/var/run/docker.sock" force_pull: false