GitHub Runner

GitHub Actions Runner is the application that executes jobs from your GitHub Actions workflows, letting you self-host runners on your own servers to build and…

  • Development
  • Other
  • Tools & Utilities
GitHub Actions Runner is the application that executes jobs from your GitHub Actions workflows, letting you self-host runners on your own servers to build and test your code in your environment.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

68/100 Good

Maintained
100last commit 4 days ago
Popular
766,399 GitHub stars
Easy to install
251 install platform, install notes
Light to run
107 GB minimum RAM
Security check
82no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 6.5/10

Availability: platform listings confirmed today

GitHub stars
6,399
Open issues
558
Last commit
2026-11-17
Latest release
v2.338.2
License
MIT
Activity
steady

Checked 4 days ago - source: GitHub (actions/runner)

Resources & Compatibility

Minimum requirements: 7 GB RAM, 2 CPU core(s), 14 GB disk.

Checked 40 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Tell it which GitHub place to join Set RUNNER_SCOPE (repo, org, or enterprise) and the matching value such as REPO_URL, ORG_NAME, or ENTERPRISE_NAME before starting. Without this, the runner does not know where to register, so it will not show up in GitHub or run jobs. source
  • Give it a token or app key Provide a personal access token (a password-like GitHub credential), a GitHub App private key, or a runner token that was created beforehand. If this login info is missing or wrong, the container cannot authenticate and first-run setup fails before it can accept jobs. source
  • Back up the runner's saved settings The runner stores its settings in /actions-runner/.runner and may also use a persistent folder like CONFIGURED_ACTIONS_RUNNER_FILES_DIR; back up that folder and keep its permissions intact. If it is lost, corrupted, or unreadable, the runner may lose its saved name, labels, or configuration and may need to be set up again. source
  • Register and start the runner Configure the runner with ./config.sh --url <owner>/<repo> --token <token>, then start it with ./run.sh; run it as a systemd service so it restarts automatically. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What must be set before starting a Docker-based GitHub Actions runner?

Set RUNNER_SCOPE and the matching value such as REPO_URL, ORG_NAME, or ENTERPRISE_NAME. You also need to provide a personal access token, GitHub App private key, or pre-created runner token.

What runner configuration should be backed up when using the community Docker runner?

Back up the runner settings in /actions-runner/.runner and any persistent folder such as CONFIGURED_ACTIONS_RUNNER_FILES_DIR. Keep the folder permissions intact so the runner can still read its saved name, labels, and configuration.

Does GitHub provide an official container image for self-hosted runners?

No, GitHub does not provide an official container image for self-hosted runners. Running GitHub Actions runners in containers is possible but not officially supported, so people often use community-maintained images.

Can a self-hosted runner be online while workflow jobs remain queued?

Yes, users report self-hosted runners that appear online but randomly leave jobs stuck in the queued state. This can happen across different workflow steps at different times.

What network access does the host machine need for a self-hosted runner?

The host machine must have appropriate network access with at least 70 kilobits per second upload and download speed.

Answers sourced from docs.github.com, github.com, stackoverflow.com, www.reddit.com

Community

Collected 48 days ago - public community threads