GitHub Actions

An experimental Docker image that runs self-hosted GitHub Actions runners with Docker support for CI teams whose jobs require containers.

  • Automation
  • Development
  • Tools & Utilities
An experimental Docker image that runs self-hosted GitHub Actions runners with Docker support for CI teams whose jobs require containers.

Platform availability

Available on 0 of 10 platforms

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

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

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

First-install notes

  • Pick runner scope and fill required GitHub details Set RUNNER_SCOPE to repo, organization, or enterprise, and provide the matching REPO_URL, ORG_NAME, or ENTERPRISE_NAME. The entrypoint checks these first, so the runner will not start if they are missing or don't match. source
  • Choose an auth method and keep the credential safe Provide a personal access token (a long password-like token), a GitHub App private key, or a pre-created runner token. This is what registers the runner with GitHub, and without a valid one it cannot pick up jobs. source
  • Enable Docker if your jobs need it Set START_DOCKER_SERVICE=true if your workflows need to build or run containers. The container starts Docker only when this is enabled, so job steps that use Docker will fail without it. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which GitHub scope settings must be correct before the runner container starts?

Set RUNNER_SCOPE to repo, organization, or enterprise, and provide the matching REPO_URL, ORG_NAME, or ENTERPRISE_NAME. The entrypoint checks these first, so the runner will not start if they are missing or do not match.

What credential options can register the self-hosted runner with GitHub?

Provide a personal access token, a GitHub App private key, or a pre-created runner token. A valid credential is required to register the runner with GitHub and allow it to pick up jobs.

How do workflows that need Docker work with this image?

Set START_DOCKER_SERVICE=true when workflows need to build or run containers. Docker is started only when this is enabled, and job steps that use Docker will fail without it.

How can sensitive deployment data be kept secure for runner workflows?

Store sensitive values in GitHub's encrypted secrets feature rather than exposing them in logs or to unauthorized users.

How can operators diagnose a self-hosted runner that is not behaving as expected?

Use GitHub's monitoring and troubleshooting capabilities to view runner activity and diagnose common issues.

Answers sourced from docs.github.com, github.com, github.com

Community

Collected 48 days ago - public community threads