You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supports both Debian 13 and Alpine 3.24. The installer prompts for the OS or accepts var_os=alpine / var_os=debian.
To register the runner, obtain a registration token in Gitea under Site Administration > Actions > Runners, then run: gitea-runner -c /etc/gitea-runner/config.yaml register --instance <URL> --token <TOKEN>.
After registering, start the runner daemon service with systemctl start gitea-runner (Debian) or rc-service gitea-runner start (Alpine).
Docker is installed and enabled by default for containerized workflow execution. Ensure nested virtualization is enabled on the LXC.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
The runner remains offline in Gitea. The installed systemd service exits with status 1/FAILURE and repeatedly restarts.
Error log
Error: invalid configuration: cache.dir is unset and the user home directory could not be determined: $HOME is not defined
gitea-runner.service: Main process exited, code=exited, status=1/FAILURE
gitea-runner.service: Failed with result 'exit-code'.
The installed unit specifies neither User= nor Environment=HOME=.... Setting WorkingDirectory= alone does not provide $HOME. With cache.dir unset, the runner fails during configuration validation.
Expected behavior
The installed service should provide the environment or explicit cache configuration required for the runner to start.
Confirmed workaround
Created /etc/systemd/system/gitea-runner.service.d/home.conf:
⚠️Marked as stale.gitea-runner since this issue was opened:
only 6 successful install(s) in the last 7 days (15 needed), 83 install(s) in total
This issue will be closed due to lack of testing 7 days after this label, unless it recovers first: the label is removed again automatically once the script has 15 successful installs in 7 days (or more than 100 installs in total) and, past 50 installs, a success rate of at least 75% (aborted and no-result runs count as failed). Maintainers can add keep-open to skip this check.
Activity
github-actions commentedon Sep 29, 2026
The Gitea Runner script is ready for testing:
Supports both Debian 13 and Alpine 3.24. The installer prompts for the OS or accepts var_os=alpine / var_os=debian.
To register the runner, obtain a registration token in Gitea under Site Administration > Actions > Runners, then run:
gitea-runner -c /etc/gitea-runner/config.yaml register --instance <URL> --token <TOKEN>.After registering, start the runner daemon service with
systemctl start gitea-runner(Debian) orrc-service gitea-runner start(Alpine).Docker is installed and enabled by default for containerized workflow execution. Ensure nested virtualization is enabled on the LXC.
Note: This is not in the official repo yet—it's just a dev version! After merging into ProxmoxVE, it will need to be recreated.
Discord testing thread: https://discord.com/channels/1302816934508630047/1554452003214852158
fabianschmeltzer commentedon Oct 28, 2026
Title: Gitea Runner fails to start:
cache.dirunset and$HOMEnot defined in systemd serviceInstallation
Installed using the [Gitea Runner Community Script](https://community-scripts.org/scripts/gitea-runner).
Installed runner version:
v5.2.4.Problem
The runner remains offline in Gitea. The installed systemd service exits with status
1/FAILUREand repeatedly restarts.Error log
Relevant service configuration
File:
/etc/systemd/system/gitea-runner.serviceThe installed unit specifies neither
User=norEnvironment=HOME=.... SettingWorkingDirectory=alone does not provide$HOME. Withcache.dirunset, the runner fails during configuration validation.Expected behavior
The installed service should provide the environment or explicit cache configuration required for the runner to start.
Confirmed workaround
Created
/etc/systemd/system/gitea-runner.service.d/home.conf:Then applied the change:
The service subsequently remained
active (running), loggeddeclare successfully, and immediately picked up a workflow job.Suggested fix
Ensure the installer configures a suitable
HOMEfor the service or explicitly sets a writablecache.dir.MickLesk commentedon Oct 28, 2026
Fixed in #3a85b87
1MisterT commentedon Nov 4, 2026
Alpine Install git command missing
also not available in container console after adding id with
apk add giteveryting worked fine :Dgithub-actions commentedon Nov 13, 2026
📊 Install telemetry for
gitea-runnerRuns reported by the DevScripts version of this script since this issue was opened (2026-09-24).
Last run: 16.11.2026 at 20:03 UTC (30 minutes ago) · success
Last success: 2026-11-16 20:06 UTC · Last failure: 2026-11-14 16:20 UTC · Avg. install time: 3 min
Failures by cause
1General error/usr/local/bin/gitea-runner register --no-interactive --config /etc/gitea-runner/config.yaml --instance "${var_gitea_url}" --token "${var_gitea_token}" --name "$(hostname)"118LXC: No IP assigned to container after timeoutNo IP assigned to CT 113 after 60 attempts6curl: DNS resolution failed (could not resolve host)curl: (6) Could not resolve host: 4d3e0f26919f429c2b0092fb846c818a.r2.cloudflarestorage.comOpen in the telemetry dashboard · updated hourly · last refresh 2026-11-16 20:33 UTC
github-actions commentedon Nov 13, 2026
gitea-runnersince this issue was opened:This issue will be closed due to lack of testing 7 days after this label, unless it recovers first: the label is removed again automatically once the script has 15 successful installs in 7 days (or more than 100 installs in total) and, past 50 installs, a success rate of at least 75% (aborted and no-result runs count as failed). Maintainers can add
keep-opento skip this check.github-actions commentedon Nov 16, 2026
A PR has been created for gitea-runner: community-scripts/ProxmoxVE#18782
MickLesk commentedon Nov 16, 2026
Merged with #18782 in ProxmoxVE
github-actions commentedon Nov 16, 2026
Files deleted with PR #2675