# Install gitea-runner with Homebrew, apk, pacman, winget Official Actions runner for Gitea. Version 3.0.1 via Homebrew; verified 2026-08-03. Also installable with apk: sudo apk add gitea-runner. ## Install ```sh sudo av install brew:gitea-runner ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install gitea-runner ``` Evidence: local Homebrew formula metadata ### Linux - apk (92%): ```sh sudo apk add gitea-runner ``` Evidence: Alpine Linux edge package indexes: gitea-runner from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz - pacman (92%): ```sh sudo pacman -S gitea-runner ``` Evidence: Arch Linux sync databases: gitea-runner from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz ### Windows - winget (92%): ```sh winget install --id Gitea.Runner -e ``` Evidence: Windows Package Manager source index: Gitea.Runner from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:gitea-runner - **Package manager:** Homebrew - **Version:** 3.0.1 - **Source summary:** Official Actions runner for Gitea - **Homepage:** - **Last updated:** 2026-08-03T00:17:51Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - gitea-runner (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 3.0.1 ## Project history and usage Gitea Runner is the official runner for Gitea Actions, the workflow automation system used by Gitea installations. It gives self-hosted Gitea sites a worker process that can register with an instance, accept jobs, and execute GitHub Actions-style workflows through Docker or host execution labels. ### Project history The runner codebase descends from the act-runner effort around Gitea Actions. The official repository's Git history begins in 2019 with support for GitHub Actions-style execution, while the Gitea-runner release stream begins with v0.0.1 in 2023 and reaches the renamed Gitea Runner 1.x and 2.x series in 2026. The project evolved from a companion binary for early Actions support into a documented part of the Gitea platform. Its README and Gitea documentation describe binary, container, Docker-in-Docker, rootless Docker-in-Docker, cache server, label, and post-task-script modes, reflecting the operational concerns of running CI workers for many repositories. ### Adoption history Adoption follows Gitea Actions itself: administrators enable Actions on a Gitea instance, create or obtain runner registration tokens, and attach one or more runner processes to supply build capacity. Packaging in Homebrew, Alpine, Arch, and WinGet makes the runner fit the same self-hosted deployment culture as Gitea. ### How it is used Practitioners use Gitea Runner by generating or supplying a YAML config, registering the runner with a Gitea instance URL and token, then running the daemon. Container deployments often mount the Docker socket or run Docker-in-Docker images so workflow jobs can execute inside job containers. Labels are central to day-to-day use: a label such as an Ubuntu image or a host execution label controls which workflows can target the runner and how jobs are launched. Operators also configure cache behavior, ephemeral runners, registration state, and cleanup scripts when they need repeatable CI nodes. ### Why package nerds care For package-manager users, Gitea Runner is the small binary that turns a packaged Gitea server from code hosting into a self-contained CI system. It matters because it avoids a separate hosted CI dependency while keeping the workflow syntax close to GitHub Actions. ### Timeline - 2019: Runner repository history begins with GitHub Actions-style execution work. - 2023: v0.0.1 appears in the runner release stream. - 2026: v1.0.0 and v2.0.0 mark the renamed Gitea Runner series. ### Related projects - Gitea Runner is closely tied to Gitea, Gitea Actions, workflow files in repositories, and the nektos/act ecosystem that influenced local execution of GitHub Actions workflows. ### Sources - - - ## Security Notes formula declares a Homebrew service. - **Geiger risk:** orange / medium - formula declares a Homebrew service ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: ./config.yaml ## Credential files - Unix: ./.runner ## Other Package-Manager Records - apk - gitea-runner - 3.0.0-r0: normalized package name match | Alpine Linux edge package indexes: gitea-runner from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Official runner for Gitea | https://gitea.com/gitea/runner - apk - gitea-runner-openrc - 3.0.0-r0: normalized package name match | Alpine Linux edge package indexes: gitea-runner-openrc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Official runner for Gitea (OpenRC init scripts) | https://gitea.com/gitea/runner - pacman - gitea-runner - 3.0.0-1: normalized package name match | Arch Linux sync databases: gitea-runner from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Official runner for Gitea | https://gitea.com/gitea/runner - winget - Gitea.Runner: normalized package name match | Windows Package Manager source index: Gitea.Runner from https://cdn.winget.microsoft.com/cache/source.msix ## Combined YAML source View the package source record on GitHub. [combined/gitea-runner.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gitea-runner.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph