Compare commits

...

2 Commits

Author SHA1 Message Date
Nikola Derežić
64761ffe59 (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
2026-01-09 13:40:09 +01:00
Nikola Derežić
c16baa5ef5 (fix) the gitea runner image was incorrect 2026-01-09 10:51:15 +01:00
2 changed files with 2 additions and 2 deletions

View File

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

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).