CI Runner Farm - Nightly

CI Runner Farm - Nightly is an early-access Unraid build of CI Runner Farm that runs concurrent, resource-capped GitHub Actions or GitLab continuous…

  • Development
  • Infrastructure
  • Network Services
  • Plugins
  • Productivity
  • Tools & Utilities
CI Runner Farm - Nightly is an early-access Unraid build of CI Runner Farm that runs concurrent, resource-capped GitHub Actions or GitLab continuous integration/continuous delivery (CI/CD) runner slots as Docker containers, with warm caches, optional autoscaling, and Docker-in-Docker. It publishes main-branch builds after validation for testing unreleased mainline changes, not production. It preserves the same installed runtime and configuration contract as the stable entry, so switching channels replaces the stable fleet rather than creating a second fleet.

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.

61/100 Good

Maintained
100last commit 19 days ago
Popular
2927 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

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

GitHub stars
27
Open issues
22
Last commit
2026-11-02
Latest release
v2.0.0
License
Apache-2.0
Activity
rising

Checked 17 days ago - source: GitHub (unraid/ci-runner-farm)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • First Install GitHub is the default provider; a farm runs one provider at a time, and switching providers drains and recreates the managed slots. source
  • First Install The nightly entry shares the stable CI Runner Farm runtime and configuration contract; switching from stable replaces the managed fleet instead of creating a second fleet. source
  • Provider Constraints A farm runs one provider (GitHub or GitLab) at a time. Switching providers drains and recreates all managed runner slots with the selected provider's credentials and runtime, so plan channel or provider changes accordingly. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can I switch a CI Runner Farm from GitHub Actions to GitLab CI?

A farm runs one provider at a time. Switching providers drains and recreates the managed slots with the selected provider's credentials and runtime.

Does CI Runner Farm expose Unraid's existing Docker socket to runner jobs?

By default, each slot gets a private privileged Docker-in-Docker daemon shared through a Unix socket instead of exposing Unraid's existing Docker socket. Privileged DinD can still be capable of host compromise.

How does the farm prevent CI jobs from consuming all server resources?

Each runner slot accepts one job at a time and can have CPU and memory limits. This keeps CI from starving the rest of the host.

Which package and build caches can stay warm across jobs?

The farm can reuse npm, yarn, pnpm, Playwright, Cargo, sccache, or custom cache directories across jobs.

Does job-weight guidance change my workflow routing or runner capacity?

No, job-weight recommendations are advisory only. They never change labels, capacity, or workflow routing.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads