Files

T

alexei.dolgolyov 0bd4549af0 docs: add gitea-runner.md — Act Runner worker capacity on TrueNAS

How to configure parallel job capacity for Gitea Act Runner:
the CONFIG_FILE env var requirement, custom config.yaml mount,
and capacity tuning.

2026-04-07 19:41:35 +03:00

1.4 KiB

Raw Permalink Blame History

Gitea Act Runner — Configuring Worker Capacity (TrueNAS)

Problem

The default Gitea Act Runner (gitea/act_runner) runs with capacity: 1, meaning only one job at a time. Setting GITEA_RUNNER_RUNNER__CAPACITY env var or placing a config.yaml in the app data directory does not work on its own.

Root Cause

The runner's entrypoint (run.sh) only passes --config to act_runner daemon when the CONFIG_FILE environment variable is explicitly set. Without it, the runner ignores any config file, even if it exists at /data/config.yaml.

Solution

Create the config file in the app data directory (mounted as /data inside the container):
```
# /mnt/system_pool/app_data/gitea-runner/config.yaml
runner:
  capacity: 6
```
Set the CONFIG_FILE environment variable in TrueNAS:

Go to TrueNAS UI → Apps → Gitea Act Runner → Edit → Extra Environment Variables and add:
```
CONFIG_FILE=/data/config.yaml
```
Restart the app.

Verification

Check the runner logs after restart — concurrent jobs should now show maxParallel matching your capacity, and multiple tasks should run simultaneously.

Notes

capacity controls how many separate jobs the runner handles concurrently
maxParallel in logs refers to parallelism within a single job's matrix strategy, not the runner capacity
To generate a full default config for reference: act_runner generate-config

1.4 KiB Raw Permalink Blame History