Skip to content

Gitea Runner #2308

Closed
Closed

Description

@jellyhuck

Name of the Script

Gitea-Runner

Script Type

CT (LXC Container)

Does this script support arm64?

arm64 supported

📋 Script Details

Add a script for Gitea Runner (repo: https://gitea.com/gitea/runner/releases).

Activity

  1. github-actions commented on Sep 29, 2026

    @github-actions
    Contributor

    The Gitea Runner script is ready for testing:

    bash -c "$(curl -fsSL https://github.com/community-scripts/ProxmoxVED/raw/main/ct/gitea-runner.sh)"
    

    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.

    Discord testing thread: https://discord.com/channels/1302816934508630047/1554452003214852158

  2. fabianschmeltzer commented on Oct 28, 2026

    @fabianschmeltzer

    Title: Gitea Runner fails to start: cache.dir unset and $HOME not defined in systemd service

    Installation

    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/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'.
    

    Relevant service configuration

    File: /etc/systemd/system/gitea-runner.service

    [Service]
    Type=simple
    ExecStart=/usr/local/bin/gitea-runner daemon --config /etc/gitea-runner/config.yaml
    WorkingDirectory=/var/lib/gitea-runner
    Restart=on-failure
    RestartSec=5s
    TimeoutStopSec=3h

    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:

    [Service]
    Environment="HOME=/var/lib/gitea-runner"

    Then applied the change:

    systemctl daemon-reload
    systemctl restart gitea-runner

    The service subsequently remained active (running), logged declare successfully, and immediately picked up a workflow job.

    Suggested fix

    Ensure the installer configures a suitable HOME for the service or explicitly sets a writable cache.dir.

  3. MickLesk commented on Oct 28, 2026

    @MickLesk
    Member

    Fixed in #3a85b87

  4. 1MisterT commented on Nov 4, 2026

    @1MisterT

    Alpine Install git command missing

    Error: git clone --no-checkout https://github.com/actions/checkout /var/lib/gitea-runner/.cache/act/c80fe54aa406573f59536bcba68bb997007d3be636059ee92b272fdcfc8dadbb/git: exec: "git": executable file not found in $PATH: 

    also not available in container console after adding id with apk add git everyting worked fine :D

  5. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    📊 Install telemetry for gitea-runner

    Runs reported by the DevScripts version of this script since this issue was opened (2026-09-24).

    Installs ✅ Successful ❌ Failed ⏹️ Aborted ❔ No result Success rate
    113 97 9 7 0 85.8%

    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

    Count Exit code Error Last seen
    7 1 General 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)" 2026-10-21 23:20 UTC
    1 118 LXC: No IP assigned to container after timeout No IP assigned to CT 113 after 60 attempts 2026-10-30 20:58 UTC
    1 6 curl: DNS resolution failed (could not resolve host) curl: (6) Could not resolve host: 4d3e0f26919f429c2b0092fb846c818a.r2.cloudflarestorage.com 2026-11-14 16:20 UTC

    Open in the telemetry dashboard · updated hourly · last refresh 2026-11-16 20:33 UTC

  6. github-actions commented on Nov 13, 2026

    @github-actions
    Contributor

    ⚠️ 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.

  7. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    A PR has been created for gitea-runner: community-scripts/ProxmoxVE#18782

  8. MickLesk commented on Nov 16, 2026

    @MickLesk
    Member

    Merged with #18782 in ProxmoxVE

  9. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    Files deleted with PR #2675

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions