After extensive testing, confirmed that Docker builds are not possible in Forgejo CI due to network isolation: Tested approaches: ❌ Socket mount (/var/run/docker.sock) ❌ DinD service with TCP ❌ Buildx with various configs ❌ Direct host Docker access ❌ runs-on:docker without container Root cause: Forgejo act runner creates isolated networks for each job. No way to access Docker daemon from within these networks. Solution: Handle Docker builds separately via deployment scripts. This is a pragmatic solution that works within Forgejo's infrastructure. CI focuses on what it can do well: code quality checks. |
||
|---|---|---|
| .. | ||
| workflows | ||