I’ve been scratching my head here. I am not sure where to make the change in my stack. I am running Gitea and Act Runner in the same docker compose stack. My external DNS is showing that my Public IP is continually hitting the public url of my Gitea instance. The interval of the POST from my public IP to the target URL being every 2 seconds tells me that it is tied to the fetch_interval setting within the config.yaml file. The path also seems to support that (see screenshot below).
However in my compose stack I set the internal IP, as well as using the container name for the gitea target that the runner should be working with, not the public URL. Is there a value within the compose or config file that I am missing or setting incorrectly? Rather have it fetch completely internally between the gitea and runner rather than the runner going to the public url. The runner is indeed working, but is not fetching via the internal network as desired.
Network Analytics screenshot
gitea-act-runner:
image: docker.io/gitea/act_runner:latest
container_name: gitea-act-runner
environment:
CONFIG_FILE: /config.yaml
#GITEA_INSTANCE_URL: <gitea_local_ip>:3030
GITEA_INSTANCE_URL: http://gitea:3030
GITEA_RUNNER_REGISTRATION_TOKEN: hidden
GITEA_RUNNER_NAME: “Act Runner”
GITEA_RUNNER_LABELS: “ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04”
volumes:
- CHANGE_TO_COMPOSE_DATA_PATH/containers/gitea/gitea-runners/act-runner/config.yaml:/config.yaml
- CHANGE_TO_COMPOSE_DATA_PATH/containers/gitea/gitea-runners/act-runner/data:/data
- /var/run/docker.sock:/var/run/docker.sock
restart: unless-stopped