normogen/.forgejo
goose 46695ae2a0
All checks were successful
Lint and Build / format (push) Successful in 33s
Lint and Build / clippy (push) Successful in 1m33s
Lint and Build / build (push) Successful in 3m34s
revert(ci): remove docker-build, acknowledge Forgejo limitations
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.
2026-03-19 09:10:55 -03:00
..
workflows revert(ci): remove docker-build, acknowledge Forgejo limitations 2026-03-19 09:10:55 -03:00