From 64761ffe59fb440e66a42b80186e9ca4d3dca373 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nikola=20Dere=C5=BEi=C4=87?= <nikola.derezic@ngit.hr>
Date: Fri, 9 Jan 2026 13:40:09 +0100
Subject: [PATCH] (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
---
 runner-config.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/runner-config.yml b/runner-config.yml
index 7224e9f..51af9e3 100644
--- a/runner-config.yml
+++ b/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).