GitHub-Azure-CI-Runner-Agent
Self-hosted CI runner that executes GitHub Actions and Azure Pipelines builds directly on Unraid, with optional embedded Docker support for containerised job…
Platform availability
Available on 1 of 10 platforms
- Unraid
- 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?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.
40/100 Fair
- Maintained
- 64last commit 111 days ago
- Popular
- 61 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 22 days ago
- GitHub stars
- 1
- Open issues
- 0
- Last commit
- 2026-08-02
- Activity
- stale
Checked 7 days ago - source: GitHub (GoldnGroup/GH-AZ-Runner-Agent-Container)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Set scope, location, and auth before start Before starting, set RUNNER_SCOPE and the matching GitHub location (REPO_URL for a repository, ORG_NAME for an organization, or ENTERPRISE_NAME for an enterprise), plus a PAT (personal access token) or GitHub App key. If these are missing or wrong, the container fails its pre-flight check or cannot register the runner to receive jobs. source
- Keep the runner config folder safe Store and protect the folder where the runner keeps its registration file, usually /actions-runner, and any CONFIGURED_ACTIONS_RUNNER_FILES_DIR volume you mount. Losing or resetting it can force you to re-register the runner and may lose settings you wanted to persist. source
- If jobs use Docker, enable Docker service If your workflows need Docker, set START_DOCKER_SERVICE=true so the runner starts the Docker service inside the container. Without it, jobs that try to run Docker commands can fail even though the runner is online. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What GitHub and Azure token permissions are required?
A GitHub repository runner needs a PAT with Repository Administration read and write. An organization runner needs Organization self-hosted runners read and write, and an Azure Pipelines agent needs Agent Pools read and manage.
Where does the container store persistent configuration and runner data?
All runtime data is stored under /mnt/user/appdata/github-actions-runner-azure-pipelines-agent. The configuration persists across restarts, so the runner does not need to be re-registered.
How do I enable Docker builds inside the runner?
Set ENABLE_DOCKER to true and add --restart unless-stopped and --privileged to the container parameters. This starts a Docker daemon inside the container, so the container runs in privileged mode.
How can I run both GitHub Actions and Azure Pipelines in the same container?
Set USE_GITHUB and USE_AZDO to true. You also need to provide the matching GitHub and Azure credentials, such as GITHUB_PAT, GITHUB_URL or GITHUB_ORG, and AZP_URL with AZP_TOKEN.
How do I update the runner image?
Pull the latest image and restart the container. The container downloads or reuses the latest runner binaries on startup.
Answers sourced from github.com
Community
Collected 49 days ago - public community threads