ci: track act_runner config with Docker socket mount
Some checks failed
CI / Unit & Component Tests (push) Has been cancelled
CI / OCR Service Tests (push) Has been cancelled
CI / Backend Unit Tests (push) Has been cancelled
CI / Unit & Component Tests (pull_request) Failing after 4m31s
CI / OCR Service Tests (pull_request) Successful in 30s
CI / Backend Unit Tests (pull_request) Failing after 3m17s
Some checks failed
CI / Unit & Component Tests (push) Has been cancelled
CI / OCR Service Tests (push) Has been cancelled
CI / Backend Unit Tests (push) Has been cancelled
CI / Unit & Component Tests (pull_request) Failing after 4m31s
CI / OCR Service Tests (pull_request) Successful in 30s
CI / Backend Unit Tests (pull_request) Failing after 3m17s
Documents the NAS runner configuration needed for Testcontainers. Must be deployed to the runner host alongside the act_runner binary. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
12
runner-config.yaml
Normal file
12
runner-config.yaml
Normal file
@@ -0,0 +1,12 @@
|
|||||||
|
# runner-config.yaml — only the relevant section
|
||||||
|
container:
|
||||||
|
# passed as DOCKER_HOST inside the job container
|
||||||
|
docker_host: "unix:///var/run/docker.sock"
|
||||||
|
# whitelists the socket path so workflows can mount it
|
||||||
|
valid_volumes:
|
||||||
|
- "/var/run/docker.sock"
|
||||||
|
# appended to `docker run` when the runner spawns a job container
|
||||||
|
options: "-v /var/run/docker.sock:/var/run/docker.sock"
|
||||||
|
# keep network mode default (bridge) — Testcontainers handles its own networking
|
||||||
|
force_pull: false
|
||||||
|
|
||||||
Reference in New Issue
Block a user