towerops/.forgejo/workflows
Graham McIntire 344c6658e8 fix: use existing Docker daemon instead of starting new one (#226)
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
2026-03-29 13:28:37 -05:00
..
e2e-tests.yaml refactor: convert 6 Gleam modules to idiomatic Elixir with TDD (#196) 2026-03-28 09:52:07 -05:00
pr-tests.yaml refactor: convert 6 Gleam modules to idiomatic Elixir with TDD (#196) 2026-03-28 09:52:07 -05:00
production.yaml fix: use existing Docker daemon instead of starting new one (#226) 2026-03-29 13:28:37 -05:00
renovate.yaml chore(config): add Renovate and build workflows 2026-03-03 16:54:19 -06:00
staging.yaml prod docker change (#221) 2026-03-29 12:16:24 -05:00