ov-foundation/skills/githubrunner/SKILL.md
Self-hosted GitHub Actions runner with the full Overthink toolchain. Rootless-first since 2026-04 — runs as uid=1000 with passwordless sudo (no root, no cap_add: ALL). Host networking retained for reachability. MUST be invoked before building, deploying, configuring, or troubleshooting the githubrunner image.
npx skillsauth add overthinkos/overthink-plugins githubrunnerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Self-hosted GitHub Actions runner with the full Overthink toolchain.
Shares the rootless-first posture with /ov-foundation:fedora-ov,
/ov-coder:arch-ov, and /ov-coder:fedora-coder.
| Property | Value | |----------|-------| | Base | fedora | | Layers | agent-forwarding, github-runner, ov-full, dbus | | Platforms | linux/amd64 | | UID / user | 1000 / user (rootless-first since 2026-04) | | Network | host | | Security | layer-level only | | Registry | ghcr.io/overthinkos |
fedora (quay.io/fedora/fedora:43)ov-full): ov + virtualization + gocryptfs + socatgithub-runner — Actions runner agent, skopeo, podman, buildahdbus — session bus (for runner hooks)Previously ran as uid: 0 / user: root with cap_add: [ALL] +
security_opt: [label=disable, seccomp=unconfined]. That legacy
posture was dropped once the /ov-foundation:container-nesting kernel
RCA proved surgical unmask=/proc/* works without caps. See
/ov-foundation:fedora-ov for the full rationale and
/ov-foundation:container-nesting for the mount_too_revealing() RCA.
The /ov-foundation:github-runner layer and runner-hook scripts still
invoke sudo where they genuinely need root (e.g. for system-level
docker setup). Passwordless sudo is provided indirectly — if you
need it for your workflows, compose /ov-coder:sshd into the
layer list (it installs /etc/sudoers.d/ov-user).
Unlike /ov-foundation:fedora-ov and /ov-coder:arch-ov, githubrunner
does NOT compose /ov-foundation:container-nesting directly. Nested
rootless podman works only via ov-full's transitive dependency
chain. If your Actions workflows need first-class rootless nested
containers (with /dev/fuse + unmask=/proc/* security opts), add
container-nesting to the layer list explicitly.
For most CI workloads that spawn containers via docker/podman against the host socket (host networking covers it), the current composition is enough.
ov config githubrunner -e RUNNER_ORG=myorg -e RUNNER_TOKEN=<token>
# post_enable hook runs config.sh --unattended
Removal deregisters via pre_remove hook:
ov remove githubrunner -e RUNNER_TOKEN=<token>
ov image build githubrunner
ov config githubrunner -e RUNNER_ORG=myorg -e RUNNER_TOKEN=<token>
ov start githubrunner
ov stop githubrunner
ov remove githubrunner -e RUNNER_TOKEN=<token>
/ov-foundation:github-runner — runner agent, hooks, security config/ov-coder:ov-full — ov + virtualization + gocryptfs + socat/ov-foundation:virtualization — QEMU/KVM + rootless libvirt session daemon/ov-foundation:container-nesting — not composed here by default (add if workflows need first-class rootless nested containers)/ov-foundation:fedora — parent base/ov-foundation:fedora-ov — sibling uid=1000 ov toolchain (includes container-nesting directly)/ov-coder:arch-ov — Arch counterpart of fedora-ov/ov-coder:fedora-coder — kitchen-sink dev image sharing the same security posture/ov-selkies:selkies-desktop-ov — non-desktop alternative streaming-desktop with the same rootless posture/ov-core:config — deploy setup with RUNNER_ORG / RUNNER_TOKEN/ov-core:start, /ov-core:stop, /ov-core:remove — lifecycle + pre-remove deregistration/ov-core:status, /ov-core:logs — verify runner is idle + troubleshootAfter ov start:
ov status githubrunner — container runningov service status githubrunner — all services RUNNINGov shell githubrunner -c "id" — uid=1000(user)MUST be invoked when the task involves the githubrunner image, self-hosted runners, or GitHub Actions CI/CD. Invoke this skill BEFORE reading source code or launching Explore agents.
/ov-build:image — image family umbrella (image: entries in overthink.yml, build/validate/inspect/list)/ov-build:build — build.yml vocabulary (distros, builders, init-systems)tools
Use when authoring or modifying a charly PLUGIN — a candy with a `plugin:` block that contributes Providers (verbs/kinds/deploy-targets/steps/builders/commands), its own CUE schema, builtin (compiled-in) or external (out-of-tree git repo). Covers the unified Provider model, the per-plugin CUE-schema contract (single source → Go params for dev + schema-over-Describe RPC for runtime), the SDK, and the loader.
tools
The CUE data-validation / configuration CLI (cue), pinned to v0.16.1. Use when working with the cue candy, installing the cue binary into a box or onto a target:local dev host, or running the offline schema-vendoring pipeline that feeds charly's egress validation.
tools
CUE EGRESS validation — validating (and, where it adds value, generating) the config files charly WRITES to a system BEFORE the bytes hit disk. MUST be invoked before working on charly/egress.go, the vendored schemas under candy/plugin-egress/egress-schemas/vendor/, the ValidateEgress / registerVendoredEgressKind path, the offline `task cue:vendor` pipeline, or adding an egress schema for any written artifact (cloud-init, k8s manifests, traefik routes, runtime config, install ledger, systemd/quadlet units, ssh_config, libvirt XML).
tools
Kubernetes cluster-probe declarative check verb — the `kube:` check verb (nodes, pods, ingress, storage class, addon health, apply/delete, and arbitrary resource GETs) served out-of-process by the candy/plugin-kube plugin (vendored client-go; no external kubectl required).