The CI runner already has a working Docker daemon and the runner user is in the docker group. All previous failures were caused by the workflow trying to start a NEW dockerd instance with vfs storage driver. Solution: Remove all daemon startup code and just use the existing Docker daemon directly. The runner user already has access via group membership. Verified on ci host: - Docker service running: overlayfs storage driver - runner user in docker group: uid=1001(runner) groups=1001(runner),989(docker) - docker info works as runner user This is the simplest solution and should have been tried first. Reviewed-on: graham/towerops-web#226 |
||
|---|---|---|
| .. | ||
| e2e-tests.yaml | ||
| pr-tests.yaml | ||
| production.yaml | ||
| renovate.yaml | ||
| staging.yaml | ||