feat(ci): re-enable dependency caching (runner cache server fixed) #108

Merged
ffaerber merged 1 commits from feat/reenable-cache-runner-fixed into main 2026-07-07 17:57:34 +02:00
Owner

Runner cache server is now reachable from job containers — root cause was Docker bridge isolation: jobs ran on docker0 while the act_runner cache server sits on gitea-ci_default. Fixed on the runner by setting container.network: gitea-ci_default in its config.yaml (verified: a container on that network gets HTTP 404 from the cache server = reachable; on docker0 it was HTTP 000 = timeout).

Re-adding the two actions/cache steps (opencode + Playwright/npm) reverted in #107. Still continue-on-error as a safety net.

Runner cache server is now reachable from job containers — root cause was Docker bridge isolation: jobs ran on `docker0` while the `act_runner` cache server sits on `gitea-ci_default`. Fixed on the runner by setting `container.network: gitea-ci_default` in its `config.yaml` (verified: a container on that network gets HTTP 404 from the cache server = reachable; on `docker0` it was HTTP 000 = timeout). Re-adding the two `actions/cache` steps (opencode + Playwright/npm) reverted in #107. Still `continue-on-error` as a safety net.
ffaerber added 1 commit 2026-07-07 17:57:25 +02:00
feat(ci): re-enable actions/cache — runner cache server now reachable
ci / lint (pull_request) Successful in 11s
ci / lint (push) Skipped
d4941ab6d6
ffaerber added 1 commit 2026-07-07 17:57:26 +02:00
feat(ci): re-enable actions/cache — runner cache server now reachable
ci / lint (pull_request) Successful in 11s
ci / lint (push) Skipped
d4941ab6d6
ffaerber merged commit 7abbbb1b8d into main 2026-07-07 17:57:34 +02:00
ffaerber deleted branch feat/reenable-cache-runner-fixed 2026-07-07 17:57:35 +02:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gitea/agents#108