Self-Hosted Linux x86_64 GitHub Actions Runners
Short answer: Strict enrolls any x86_64 Linux machine as a zero-sudo systemd --user service, validates loginctl enable-linger so runners survive SSH disconnects, prunes idle Docker layers in Tier 5, and auto-balances multi-slot loads.
Run high-core Linux CI on dedicated workstations or bare-metal servers with linger checks and Docker cache hygiene.
Drop-in workflow YAML & zero-sudo enrollment
Enroll your host with strict add-runner and route jobs directly via GitHub's native runs-on labels:
jobs:
test:
runs-on: [self-hosted, Linux, X64]
steps:
- uses: actions/checkout@v4
curl -fsSL https://strict.ai/install.sh | sh
strict add-runner owner/repo --labels self-hosted,Linux,X64
How Strict keeps Linux x86_64 runners healthy
| Subsystem | How it applies to Linux x86_64 |
|---|---|
| Disk Cleanup | Tiers 1–3 clear runner diagnostics, npm/bun/cargo caches, and git-ignored build leftovers; Tier 5 prunes dangling Docker objects idle longer than 24 hours. |
| Preflight Doctor | linux-linger verifies loginctl enable-linger; dns-github checks GitHub API resolution; disk-headroom and tailscale-health guard uptime. |
| Tracked Toolchains | docker, node, bun, python, rust, go, gh, java, runner |
| Cache & Balancing | Local NVMe Docker BuildKit layers stay warm without $0.50/GB sticky disk fees, while Tailnet Build Cache serves ACTIONS_CACHE_URL across your fleet. |
When Strict fits vs. when hosted runners win
Use Strict for Linux x86_64 when
- $0/min compute on 8–64 core office boxes or bare-metal Linux nodes
- Zero-sudo systemd --user units verified by linux-linger preflight checks
- Proportional slot draining prevents CPU thrashing under monorepo spikes
Use cloud-hosted runners when
- Sudden 100-way parallel test sharding needed once a week with idle servers otherwise
- Public fork PR CI requiring single-use microVM isolation
Frequently asked questions
Do Linux runners stay alive after I log out of SSH?
Yes, when lingering is enabled on your user account. Strict's linux-linger doctor check specifically verifies loginctl enable-linger so systemd --user services persist across logouts and reboots.
Does Strict require root or sudo on Linux build servers?
No. Strict installs its Python agent and GitHub actions/runner units under your user systemd session with 0600 token permissions and no root daemon.
Can Linux x86_64 hosts share a cache with Mac runners?
Yes. Strict's Tailnet Build Cache exposes standard GitHub Actions cache endpoints over your Tailscale tailnet so both Linux and macOS nodes benefit.
Try Strict on one spare Mac in under two minutes
Signed Apple Silicon app or single-line CLI · Zero accounts required