Gitea Runner
Gitea Runner runs Gitea Actions jobs. It asks a Gitea instance for jobs, runs them, and sends their logs and results back.
Requirements
Section titled “Requirements”- Gitea 1.21 or later with Actions enabled, the default setting.
- Git 2.34.1 or later on the runner’s
PATH. - Docker, or Podman with
podman.socketenabled, for jobs in containers, Docker actions, anddocker://steps.
Jobs need these tools wherever steps run, in the job image or on the host:
bashorshforrunsteps, orpwshorpowershellon Windows.nodefor JavaScript actions andhashFiles().git2.34.1 or later forbuiltin:checkout, plusgit-lfsfor itslfsinput andsshfor itsssh-keyinput.
Where jobs run
Section titled “Where jobs run”The runner’s labels determine where each job runs. One runner can use a mix of these environments:
| Label | Where the job runs |
|---|---|
docker://<image> |
In a container |
kubernetes://<image> |
In a pod in a Kubernetes cluster |
host |
Directly on the runner’s machine |
Host jobs run as the runner’s user without isolation. Use them only for trusted repositories.
Getting started
Section titled “Getting started”- Install the runner from a binary, with Docker, or on Kubernetes.
- Register it with your Gitea instance.
- Start it with
gitea-runner daemon.
The runner works without a configuration file. Configuration explains when you need one.
The runner is released independently of Gitea. Read Upgrading before moving to a new major version.