Przejdź do treści
Biblioteka skilli
DevOps i chmura · Automatyzacja

github-runner

/github-runner

Wdraża, zarządza i diagnozuje własne runnery GitHub Actions: usługa systemd, kontenery Docker, Kubernetes (Actions Runner Controller) i Scale Set Client, w tym autoskalowanie i utwardzanie bezpieczeństwa.

Repozytorium
agent-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
25.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
12
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 25.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Wdraża, zarządza i diagnozuje własne runnery GitHub Actions: usługa systemd, kontenery Docker, Kubernetes (Actions Runner Controller) i Scale Set Client, w tym autoskalowanie i utwardzanie bezpieczeństwa.

Oryginalny opis (EN)

Deploy, manage, and troubleshoot self-hosted GitHub Actions runners. Covers systemd service, Docker containers, Kubernetes (Actions Runner Controller), and the Scale Set Client. Use when setting up a CI runner, debugging registration failures, designing autoscaling, or hardening runner security. Do not use this skill for unrelated requests; route to the nearest named specialist.

Jak działa

  1. When to Use
  2. Quick Reference
  3. Sequential Workflow
  4. Templates
  5. Reference Files
Sekcje z nagłówków SKILL.md, w oryginale · 113 linii, 836 słów
Podgląd SKILL.md
---
name: github-runner
description: >-
  Deploy, manage, and troubleshoot self-hosted GitHub Actions runners. Covers systemd
  service, Docker containers, Kubernetes (Actions Runner Controller), and the Scale Set
  Client. Use when setting up a CI runner, debugging registration failures, designing
  autoscaling, or hardening runner security. Do not use this skill for unrelated requests;
  route to the nearest named specialist.
license: MIT
compatibility: Linux, macOS, or Windows target hosts. Docker for containerized runners.
  Kubernetes for ARC deployments.
metadata:
  tags: github-actions, ci-cd, runners, devops, docker, kubernetes, autoscaling
  source: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners
  version: 1.0.2
---

# Self-Hosted GitHub Actions Runner

Deploy and manage self-hosted GitHub Actions runners — the machines that execute CI/CD workflow jobs. Self-hosted runners give you control over hardware, OS, and toolchain, at the cost of requiring you to maintain the environment.

## When to Use

| Trigger | What to do |
|---------|------------|
| "Set up CI for my project", "deploy a self-hosted runner for [repo/org]" | Read [deployment](references/deployment.md) — choose systemd, Docker, or ARC |
| "Runner won't register / keeps failing", "runner gets 404", "registration token expired" | Read [management](references/management.md) — ACCESS_TOKEN vs RUNNER_TOKEN, groups |
| "How to scale runners automatically", "auto-scale runners", "too many queued jobs" | Read [scaling](references/scaling.md) — ARC, Scale Set Client, ephemeral |
| "Secure my self-hosted runners", "hardening runners", "runner security", "public repo risk" | Read [security](references/security.md) — public repo risks, ephemeral, JIT, groups |
| "Make a custom runner image", "build a runner Dockerfile", "custom runner with Python" | Read [custom-images](references/custom-images.md) — Dockerfile, ARC container modes |
| "What domains does a runner need to reach?", "runner firewall rules", "runner network setup" | Read [network](references/network.md) — firewall rules, TLS, proxy |
| "Labels, groups, or both for routing?", "how to target specific runners" | Read [management](references/management.md) — labels and groups sections |
| "Monitor / troubleshoot runner issues", "runner offline", "runner not picking up jobs" | Read [management](references/management.md) — monitoring and troubleshooting sections |

## Quick Reference

### Deployment Spectrum

| Approach | Complexity | Autoscaling | Best For |
|----------|------------|-------------|----------|
| systemd service | Low | Manual | Single machine, simple CI |
| Docker container | Medium | Manual replicas | Homelab, small team |
| ARC (Kubernetes) | High | Built-in | Teams with K8s expertise |
| Scale Set Client | High | Custom | Non-K8s platform teams |

### Critical: ACCESS_TOKEN vs RUNNER_TOKEN

This is the most common setup failure. The `myoung34/github-runner` Docker entrypoint **unexports `RUNNER_TOKEN`** at startup — it's only used for **de-registration**. Registration requires `ACCESS_TOKEN` (a GitHub PAT).

| Token | Purpose | Expiry |
|-------|---------|--------|
| `ACCESS_TOKEN` | Registration — generates fresh tokens via GitHub API | Long-lived (PAT) |
| `RUNNER_TOKEN` | **De-registration only** — NOT for initial registration | 60 min |

**PAT scopes:**
- Repo-level: `repo`
- Org-level: `admin:org`
- Enterprise-level: `manage_runners:enterprise`

### Labels Strategy

Default labels: `self-hosted` + OS (`linux`/`windows`/`macOS`) + arch (`x64`/`ARM`/`ARM32`/`ARM64`)

Common convention: `self-hosted,<hostname>,<os>,<arch>,<project>`. In workflows:

```yaml
runs-on: [self-hosted, linux, x64, gpu]
```

All labels must match (AND logic). Use `--no-default-labels` to strip OS/arch auto-labels.

### Key Pitfalls

| Problem | Cause | Fix |
|---------|-------|-----|
| 404 on POST to runner-registration | `RUNNER_TOKEN` used instead of `ACCESS_TOKEN` | Switch to `ACCESS_TOKEN` with PAT |
| "Could not find any self-hosted runner group named 'Default'" | Org uses different group name | Check groups via `gh api`, set `RUNNER_GROUP` |
| "Ephemeral option is enabled" when not wanted | `EPHEMERAL=0` — truthy in bash | Use `EPHEMERAL=false` (string) |
| `docker compose down -v` wipes credentials | Named volumes deleted | With `ACCESS_TOKEN`, auto-recovers |
| Runner can't see host filesystem paths | Runner runs inside Docker container | Write deploy configs inline in workflow |
| Hugo build: "Go not found" | No Go on Ubuntu 20.04 runner | `hugo mod vendor` and commit `_vendor/` |
| GHCR pull "unauthorized" | No Docker registry auth in deploy job | Add `docker/login-action@v4` |
| Runner offline >14 days | Auto-removed by GitHub | Register a new runner |

## Sequential Workflow

### 1. Choose deployment approach

Read [deployment](references/deployment.md) and select systemd, Docker, ARC, or Scale Set Client.

### 2. Figure out what runner scope you need

- **Repo-level**: Runner scoped to a single repo — you need admin access
- **Org-level**: Runner shared across repos in an org — you need org owner access
- **Enterprise-level**: Runner shared across orgs in an enterprise — you need enterprise access

### 3. Register the runner

Read the [architecture](references/architecture.md) reference for the registration flow.

### 4. Route jobs to the runner

Use `runs-on` with labels and optionally groups. Read [management](references/management.md) labels section.

### 5. Monitor and troubleshoot

Read the [management](references/management.md) troubleshooting section when things go wrong.

### 6. Plan for security and scaling

Read [security](references/security.md) and [scaling](references/scaling.md) for production deployments.

## Templates

- [templates/docker-compose.yml](templates/docker-compose.yml) — Docker runner with `myoung34/github-runner`
- [templates/custom-runner.Dockerfile](templates/custom-runner.Dockerfile) — Custom runner image for ARC

## Reference Files

| File | Load when |
|------|-----------|
| [references/architecture.md](references/architecture.md) | You need to understand registration flow, job lifecycle, or runner communication |
| [references/deployment.md](references/deployment.md) | You need to deploy a runner — systemd, Docker, ARC, or Scale Set Client |
| [references/security.md](references/security.md) | You need to harden runners, set up ephemeral/JIT, configure groups |
| [references/scaling.md](references/scaling.md) | You need autoscaling — ARC, Scale Set Client, or webhook-driven |
| [references/management.md](references/management.md) | You need groups, labels, monitoring, troubleshooting, or cleanup |
| [references/custom-images.md](references/custom-images.md) | You need a custom runner Dockerfile, ARC Kubernetes mode |
| [references/network.md](references/network.md) | You need firewall rules, proxy config, or are troubleshooting connectivity |
Pliki w paczce (12)
  • README.md 1 KB
  • SKILL.md 7 KB
  • evals/evals.json 3 KB
  • references/architecture.md 3 KB
  • references/custom-images.md 3 KB
  • references/deployment.md 6 KB
  • references/management.md 8 KB
  • references/network.md 4 KB
  • references/scaling.md 3 KB
  • references/security.md 4 KB
  • templates/custom-runner.Dockerfile 1 KB
  • templates/docker-compose.yml 1 KB

Wersje

W bazie nie ma innych skilli o nazwie github-runner.

Identyczna treść występuje jeszcze w 1 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.

Migawka bazy z 13.11.2026 · wersja paczki 09f44a839d64 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90cmk:cicd
    Konfiguruje CI/CD w repozytorium: przepływy GitHub Actions, samodzielne runnery, ochronę gałęzi i skanowanie podatności.
  • 100actions
    Tworzy i konfiguruje GitHub Actions: własne akcje, runnery, dobre praktyki bezpieczeństwa i publikację w marketplace.
  • 100incus-gha-runners
    Konfiguruje, rozszerza i naprawia samodzielnie hostowane runnery GitHub Actions na jednym hoście Linux, każdy w osobnym nieuprzywilejowanym kontenerze systemowym Incus z własnym Dockerem.
  • 100devops-deployment
    Konfiguruje potoki CI/CD, kontenery i infrastrukturę jako kod, np. GitHub Actions, Docker, Kubernetes, Helm i Terraform.
  • 100gitea-actions-and-ci
    Konfiguruje Gitea Actions, kompatybilny z GitHub Actions system CI/CD: rejestracja własnego act_runner, różnice względem GitHub Actions (konteksty, brakujące funkcje, etykiety runnerów) i diagnoza zadań bez runnera.
  • 100depot-github-runners
    Konfiguruje runnery GitHub Actions zarządzane przez Depot jako zamiennik runnerów GitHub: rozmiary CPU i RAM, etykiety runs-on, ARM, Windows, macOS, egress filtering i Depot Cache.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.