GitHub-hosted runner
A virtual machine that GitHub creates for a single job and destroys when the job ends.
In more detail
Because the machine is new every time, nothing a job leaves on disk survives to the next job, which makes builds reproducible but means files must be passed on as artifacts. It boots from a runner image that already has common tools installed.
Related terms
- runner — A machine running the runner application that picks up a queued job, runs its steps and reports the result.
- runner image — The prepared operating system disk a GitHub-hosted runner boots from, with Git, Docker, language runtimes and build tools already installed.
- self-hosted runner — A runner you install and operate on your own hardware or cloud machine, selected with the self-hosted label.
- virtual machine — A complete pretend computer, with its own operating system, running as software on a real computer.
Taught in
- Runners: Where Code Executes — Continuous Integration & Continuous Delivery Pipelines
- Securing Pipelines: Secrets Management — Continuous Integration & Continuous Delivery Pipelines
- Triggers In Depth: Filters, Schedules And Dispatch — GitHub Actions (GH-200) Exam Prep
- Three Kinds Of Action: JavaScript, Docker Container Or Composite — GitHub Actions (GH-200) Exam Prep
- GitHub-Hosted And Larger Runners: Specs, Software And Networks — GitHub Actions (GH-200) Exam Prep
- Self-Hosted Runners At Scale: Labels, Groups And ARC — GitHub Actions (GH-200) Exam Prep
- Usage, Billing And The Audit Log — GitHub Actions (GH-200) Exam Prep
- GITHUB_TOKEN: Least Privilege, Job By Job — GitHub Actions (GH-200) Exam Prep
- OIDC: Cloud Access Without Stored Keys — GitHub Actions (GH-200) Exam Prep
- Faster And Cheaper: Where The Minutes Go — GitHub Actions (GH-200) Exam Prep
- YAML-Reading Sprint: What Happens When This Runs? — GitHub Actions (GH-200) Exam Prep
- Full Mock And Review: Where Your Points Go — GitHub Actions (GH-200) Exam Prep