← Directory

Docker-Github-Actions-Runner

This will run the new self-hosted github actions runners with docker-in-docker

  • Other
  • Productivity
  • Tools & Utilities
This will run the new self-hosted github actions runners with docker-in-docker

Platform availability

Available on 1 of 6 install platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

73/100 Good

Maintained
100last commit 3 days ago
Popular
682,479 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
602 GB minimum RAM, runs on ARM
How is this calculated?

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). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today, links checked 10 days ago

GitHub stars
2,479
Open issues
1
Last commit
2026-10-06
Latest release
2.338.0
License
GPL-3.0
Activity
steady

Checked 2 days ago - source: GitHub (myoung34/docker-github-actions-runner)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 10 GB disk. ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Set runner scope and required GitHub details Before starting the container, tell it whether you're connecting to a repository, organization, or enterprise and fill in the matching variable (REPO_URL, ORG_NAME, or ENTERPRISE_NAME) plus your authentication token or GitHub App details. Without these, the container can't validate its settings and the runner will not register with GitHub. source
  • Provide a valid GitHub token or App login Use a personal access token, GitHub App private key and app details, or an already-made runner token so the container can get permission to register itself. If the login doesn't allow self-hosted runner access, the start-up process stops and no jobs will run. source
  • Let the container own its runner folders By default the container creates and fixes ownership of /actions-runner (runner config) and /_work (job files) for its runner user. If you mount your own folders for those paths, make sure they're readable/writable by the container user, or jobs may fail with permission errors. source

Fetched 10 days ago - each note links to its source

Alternatives (3)

  • Codeship - Codeship is a hosted Continuous Delivery Service that integrates with GitHub and Bitbucket.
  • GitHub Actions - An experimental Docker image that runs self-hosted GitHub Actions runners with Docker support for CI teams whose jobs require containers.
  • Woodpecker CI - Woodpecker CI is a self-hosted continuous integration and continuous delivery (CI/CD) engine that runs automated build, test, and deploy pi…

Checked 7 days ago - source: AlternativeTo

Common questions

Which environment variables tell the runner container which GitHub scope to use?

Set REPO_URL for a repository, ORG_NAME for an organization, or ENTERPRISE_NAME for an enterprise before starting the container. The matching authentication token or GitHub App details are also required.

Why can the container stop during startup and prevent jobs from running?

The startup process stops when the supplied GitHub token or App login does not allow self-hosted runner access.

What file permissions are needed if I mount my own runner or work directories?

If you mount /actions-runner or /_work, make sure the container user can read and write them. The container otherwise creates and fixes ownership of those folders for its runner user.

Does the project run Docker inside the self-hosted runner?

Yes, it runs the new self-hosted GitHub Actions runners with docker-in-docker.

Answers sourced from github.com, github.com

Community

Collected 5 days ago - public community threads