fix(gitea): runner config for caching 3

gitea/runner-config.yaml

@@ -15,24 +15,23 @@ runner:
 cache:
   enabled: true
   dir: ""
-  # "gitea_runner" (relying on shared networking via container.network below)
-  # didn't work - job containers get their own auto-created per-task network
-  # regardless of container.network (a known act_runner limitation, confirmed
-  # by inspecting a live job container: it was never attached to falcon_network
-  # at all). host.docker.internal resolves to that per-task network's own
-  # gateway instead, which *does* route back to this container's published
-  # port on the host - see https://docs.gitea.com/runner/cache/.
-  host: "host.docker.internal"
-  port: 8088
+  # Leave empty for auto-detection - it correctly finds gitea_runner's own
+  # address once job containers actually share a network with it (see
+  # container.network below; a custom network name didn't work, but Docker's
+  # real default "bridge" network does).
+  host: ""
+  port: 0
   external_server: ""
 
 container:
-  network: ""
+  # A custom network name (e.g. falcon_network) was silently ignored - job
+  # containers still got their own isolated per-task network regardless.
+  # "bridge" (Docker's real, always-present default network) is honored
+  # instead - gitea_runner joins it too (see compose.yml) so both sides can
+  # reach each other by container name/IP.
+  network: "bridge"
   privileged: false
-  # --add-host is what makes host.docker.internal (used for cache.host above)
-  # resolve inside job containers on Linux - Docker only wires it up
-  # automatically on Docker Desktop (Mac/Windows), not here.
-  options: "-v /var/run/docker.sock:/var/run/docker.sock --add-host=host.docker.internal:host-gateway"
+  options: "-v /var/run/docker.sock:/var/run/docker.sock"
   workdir_parent: ""
   valid_volumes: []
   docker_host: ""