// the find
myoung34/docker-github-actions-runner
This will run the new self-hosted github actions runners with docker-in-docker
A Docker image that runs GitHub Actions self-hosted runners, including support for Docker-in-Docker via privileged mode or sysbox. Targets teams that want to run their CI on their own infrastructure rather than GitHub-hosted runners — useful for private network access, custom hardware, cost control, or beefier machines than GitHub offers.
Supports GitHub Apps authentication in addition to PATs, which is the right way to handle this at org scale since Apps tokens are short-lived and scoped. Nightly rebuilds track the upstream runner binary automatically, so you're not stuck on a stale runner version. Multiple Ubuntu and Debian base variants give you a real choice rather than forcing everyone onto one base. The `EPHEMERAL` flag plus `RUNNER_WORKDIR_ROOT` together make autoscaling-friendly setups (one container per job, no shared state) genuinely straightforward.
The README punts almost everything to the wiki, which is a maintenance liability — wikis drift, go stale, and aren't versioned with the code. Docker-in-Docker requires privileged mode by default, which is a significant security exposure in multi-tenant or shared environments, and the docs treat this as a footnote rather than a lead warning. Environment variables are the only configuration interface, so there's no composable config file for complex setups — you end up with docker-compose files or Helm values full of env vars that are hard to review. GitHub Actions service containers and job-level Docker features simply don't work, which is a meaningful capability gap if your workflows rely on them.