silverwind
be6aefc7e8
The runner pages had drifted from the runner. They claimed Podman is unsupported, a registration retry limit of 10, a `container.env` proxy override that has no effect, and they used the deprecated `generate-config` command, while the actual instructions were buried under implementation details. The develop and 5.x pages are rewritten from the current runner sources (`main` is `v5.2.0`). They are shorter and aimed at operators, with a new page covering what jobs get. The reference generator now documents the `config` command, and the quickstart pages in every language use the `gitea-runner` binary name. Reviewed-on: https://gitea.com/gitea/docs/pulls/600 Reviewed-by: Lunny Xiao <[email protected]> Co-authored-by: silverwind <[email protected]>
2.3 KiB
sidebar_position
| sidebar_position |
|---|
| 4 |
Labels
A runner's labels determine which jobs it accepts and where it runs them. Gitea sends a job to a runner that has the labels specified in the job's runs-on. The runner uses the environment of the first matching entry in runs-on.
| Label | Job environment |
|---|---|
ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest |
Container using the specified image. |
ubuntu-latest:kubernetes://docker.gitea.com/runner-images:ubuntu-latest |
Pod using the specified image. See job pods. |
macos:host, or just macos |
The runner's machine. |
The label name is the part before the first :docker, :kubernetes or :host. Workflows use this name in runs-on. For example:
ubuntu-latest:docker://docker.gitea.com/runner-images:ubuntu-latest,macos:host
With these labels, runs-on: ubuntu-latest jobs run in a container. Jobs with runs-on: macos run on the runner's machine.
A job's container: image replaces the label's image. The job runs in a container even with a host label.
A job whose runs-on matches none of the runner's labels uses runner.default_image, which defaults to docker.gitea.com/runner-images:ubuntu-latest. It runs in a container, as a pod on runners with kubernetes but no docker labels, or on the host when no Docker daemon is reachable.
Changing labels
Labels are set during registration and stored in the registration file. To change them, set them in the configuration file or on the command line, then restart the runner. The runner reports its labels to Gitea at startup:
gitea-runner config set runner.labels 'ubuntu-latest:docker://node:24' 'macos:host'
daemon --labels or the GITEA_RUNNER_LABELS environment variable takes precedence over runner.labels. The runner.labels setting takes precedence over labels in the registration file.
Choosing images
- Use the runner images for tools that common workflows need. To avoid installing a toolchain on every run, choose an image that already includes it.
- Pin images by tag or digest for reproducible jobs.
- Give host labels distinct names such as
macos-arm64to prevent workflows written for GitHub'subuntu-latestfrom running directly on your machine without a sandbox.