How to setup Forgejo Action Runner in Coolify?

[essovius]

Hello, does anybody know how can i setup forgejo action runner? I've set up forgejo in one of my resources. It's running and working except actions.

https://coolify.io/docs/services/forgejo#forgejo-actions-runner here it says, setting environment variable and restarting is enough. But even if i did, runner doesn't appear on forgejo. I am new to this and couldn't find a source about this.

Do I have to create another service in coolify act as runner with docker compose?

Coolify includes Forgejo services with a single runner, using Docker-in-Docker to handle and report task jobs.

This says coolify includes. I am confused.

[supernaut]

I also am confused by the documentation. I've added the variable and restarted the service as instructed without results.

[devopsbrett]

I'll admit, the documentation isn't as clear as it could be but I was able to get this working. This is how I did it.

• First add the RUNNER_SHARED_SECRET environment variable to your service
• Next go to https://github.com/coollabsio/coolify/blob/v4.x/templates/compose/ and find the forgejo service that you chose for your deployment but that also includes the runner. For me I deployed Forgejo with Postgresql so I chose https://github.com/coollabsio/coolify/blob/v4.x/templates/compose/forgejo-with-runner-with-postgresql.yaml
• Copy the yaml in that file and then return to your coolify setup
• With your forgejo service opened in coolify, go to Configuration > General and click the Edit Compose File button
• Replace all the text with the yaml you copied from github and click Save
• Now click Restart and wait for the extra containers to be pulled and for the service to come back up

Now if you log back in to forgejo and visit /admin/actions/runners you should see the runner has been launched and has been picked up by forgejo

[JasterV]

I followed your steps but I've got a problem, I got this error in the register step

time="2026-04-26T19:56:57Z" level=info msg="Creating runner file"
2026-Apr-26 19:56:57
Error: ping https://git.jaster.xyz:3000 failed unavailable: dial tcp <MY-PUBLIC-IP>:3000: connect: connection refused

I was able to fix it by updating the register script to point to ${SERVICE_URL_FORGEJO} instead of ${SERVICE_URL_FORGEJO}:3000, in case anyone else has this issue :)

[JasterV]

Another issue that I had to fix manually, the runner container needs to have the DOCKER_TLS_CERTDIR: /certs environment key-value pair set in the compose file, otherwise it can't find the certs generated by docker-in-docker