(bugfix) runner config did not contain network name

- the container running the job is to use leading it not being able to access the gitea instance when trying to push new docker image to registry

docker-compose.yaml

@@ -80,7 +80,7 @@ services:
       - traefik.http.routers.gitea-registry.tls.certresolver=letsencrypt
       - traefik.http.routers.gitea-registry.service=gitea
   runner:
-    image: gitea/act-runner:0.2.13
+    image: docker.io/gitea/act_runner:0.2.13
     networks:
       - gitea-network
     restart: always

runner-config.yml

@@ -69,7 +69,7 @@ container:
   # Specifies the network to which the container will connect.
   # Could be host, bridge or the name of a custom network.
   # If it's empty, act_runner will create a network automatically.
-  network: ""
+  network: "gitea-network"
   # Whether to use privileged mode or not when launching task containers (privileged mode is required for Docker-in-Docker).
   privileged: false
   # And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway).