From 6d46e36bf39cc360e995be5c0768d0053a387493 Mon Sep 17 00:00:00 2001 From: thanhnv Date: Wed, 1 Jul 2026 13:13:53 +0900 Subject: [PATCH] fix(ci): remove duplicate docker.sock mount in act-runner options act_runner automatically passes /var/run/docker.sock from its own mounts to job containers. Explicitly adding it in container.options caused "Duplicate mount point" error, preventing all job containers from starting. Co-Authored-By: Claude Sonnet 4.6 --- AINative_OKR_CASAN5/.gitea/act-runner-config.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/AINative_OKR_CASAN5/.gitea/act-runner-config.yaml b/AINative_OKR_CASAN5/.gitea/act-runner-config.yaml index 9fb05b2..dc11b5c 100644 --- a/AINative_OKR_CASAN5/.gitea/act-runner-config.yaml +++ b/AINative_OKR_CASAN5/.gitea/act-runner-config.yaml @@ -28,9 +28,9 @@ container: network: bridge # --memory 512m: prevent OOM on 1 GB VPS (build runs in HOST daemon, not job container) - # -v socket: Docker-outside-of-Docker for the deploy job; lets docker CLI in the job - # container talk to the HOST daemon to build + run OKR images. - options: "--memory 512m --cpus 1.5 -v /var/run/docker.sock:/var/run/docker.sock" + # NOTE: act_runner already passes /var/run/docker.sock from its own mounts to job + # containers; do NOT add it here or Docker will reject the duplicate bind mount. + options: "--memory 512m --cpus 1.5" valid_volumes: - "**"