knee-cola/d-gitea
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

(bugfix) runner config did not contain network name

Browse Source 
- 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
This commit is contained in:
Nikola Derežić
2026-01-09 13:40:09 +01:00
parent c16baa5ef5
commit 64761ffe59
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
runner-config.yml
View File

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