mirror of
https://gitea.com/gitea/runner.git
synced 2026-11-05 14:55:44 +00:00
silverwind
319567213d
The README's Docker example and the Docker and Kubernetes examples pointed at `nightly` images, while the README recommends `latest-dind`. Deployments copied from them should run the latest release, not a build of `main`. None of the examples changed since v5.3.0, so they work as written with the current `latest` tags. _Written by Claude (Opus 5.5)._ Reviewed-on: https://gitea.com/gitea/runner/pulls/1383 Reviewed-by: Lunny Xiao <[email protected]> Co-authored-by: silverwind <[email protected]>
15 lines
554 B
Markdown
15 lines
554 B
Markdown
### Run `gitea-runner` in a Docker Container
|
|
|
|
The recommended Docker-in-Docker image runs its own Docker daemon for jobs, so they never get the host's Docker socket:
|
|
|
|
```sh
|
|
docker run --privileged \
|
|
-e GITEA_INSTANCE_URL=http://192.168.8.18:3000 \
|
|
-e GITEA_RUNNER_REGISTRATION_TOKEN=<runner_token> \
|
|
-v "$PWD/data:/data" \
|
|
-v runner-docker:/var/lib/docker \
|
|
--name my_runner gitea/runner:latest-dind
|
|
```
|
|
|
|
The volumes keep the runner's registration and the job image cache. See [image flavours](../../README.md#image-flavours) for alternatives.
|