bircni and silverwind
84c0fcd1fa
fix!: remove the dbfs log workaround and require Gitea 1.26.2 ( #1395 )
...
Gitea 1.26.2 finalizes logs on an empty `UpdateLog` with `NoMore` (https://github.com/go-gitea/gitea/pull/37687 ), so the sentinel row is no longer needed. On older servers, the final log of most jobs would never be archived and stays in `dbfs_data`, so this raises the minimum Gitea version. It lives in `ver.MinGiteaVersion`, which the error for servers without `Declare` now names.
Fixes: https://gitea.com/gitea/runner/issues/953
Co-authored-by: silverwind <me@silverwind.io >
Reviewed-on: https://gitea.com/gitea/runner/pulls/1395
Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com >
Co-authored-by: bircni <bircni@icloud.com >
2026-11-10 11:35:16 +00:00
78610b01f6
docs: recommend DinD for container jobs ( #1258 )
...
Make Docker-in-Docker the recommended and first-shown setup. Mounting the host's Docker socket gives every job root-equivalent access to the host, while DinD gives jobs their own daemon. The default `latest` tag is unchanged.
Also shorten the image flavour docs to what users need to pick an image, and correct that `dind-rootless` needs `--privileged` too.
Closes https://gitea.com/gitea/runner/issues/1227
---------
Co-authored-by: silverwind <2021+silverwind@noreply.gitea.com >
Co-authored-by: silverwind <me@silverwind.io >
Reviewed-on: https://gitea.com/gitea/runner/pulls/1258
Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com >
Co-authored-by: bircni <bircni@icloud.com >
2026-09-30 18:27:11 +00:00
861d351845
add apparmor=rootlesskit in security_opt ( #937 )
...
paste depends_on chain from socket-runner-setup to runner-dind-setup
add apparmor=rootlesscit in security_opt
add explanations for elevated privileges
---------
Co-authored-by: silverwind <me@silverwind.io >
Co-authored-by: silverwind <2021+silverwind@noreply.gitea.com >
Reviewed-on: https://gitea.com/gitea/runner/pulls/937
Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com >
Co-authored-by: Schallbert <schallbert@mailbox.org >
Co-committed-by: Schallbert <schallbert@mailbox.org >
2026-05-07 21:20:33 +00:00
Lunny Xiao and silverwind
13dc9386fe
Rename act_runner to runner ( #850 )
...
## Consumer-facing breaking changes
- **Go module path**: `gitea.com/gitea/act_runner` → `gitea.com/gitea/runner`. Anything importing `act/...` or `internal/...` packages (notably Gitea itself) must update imports.
- **Binary name**: `act_runner` → `gitea-runner`. Wrapper scripts, systemd units, init scripts, and documentation referencing the binary by `act_runner` will break.
- **Docker image**: `gitea/act_runner` → `gitea/runner` (incl. `*-dind-rootless` variants). Users pulling `gitea/act_runner:nightly` etc. will get stale images. Note: the image name is `gitea/runner`, not `gitea/gitea-runner`.
- **Release artifact paths**: S3 directory `act_runner/{{.Version}}` → `gitea-runner/{{.Version}}`, and artifact filenames change with the new project name. Existing download URLs break.
- **Metrics namespace**: changed from `act_runner` to `gitea_runner` (e.g. `act_runner_jobs_total` → `gitea_runner_jobs_total`); existing monitors/dashboards must be updated.
- **ldflags version path**: `gitea.com/gitea/act_runner/internal/pkg/ver.version` → `gitea.com/gitea/runner/internal/pkg/ver.version`. Affects anyone building with custom ldflags.
- **Kubernetes example resource names**: `act-runner` / `act-runner-vol` → `runner` / `runner-vol`. Users who copied the manifests verbatim will see resource churn on apply.
- **s6 service name**: `scripts/s6/act_runner/` → `scripts/s6/gitea-runner/` (image-internal; only matters for downstream image overrides).
Unchanged: YAML config field names, env vars (`GITEA_*`), CLI flags/subcommands, registration file format.
---------
Co-authored-by: silverwind <me@silverwind.io >
Reviewed-on: https://gitea.com/gitea/runner/pulls/850
Reviewed-by: Zettat123 <39446+zettat123@noreply.gitea.com >
Reviewed-by: silverwind <2021+silverwind@noreply.gitea.com >
Reviewed-by: Nicolas <bircni@icloud.com >
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-committed-by: Lunny Xiao <xiaolunwen@gmail.com >
2026-04-30 20:12:51 +00:00
stecklars and Lunny Xiao
c82077e6b5
examples: improve DIND rootless network performance ( #786 )
...
## Summary
- Add `DOCKERD_ROOTLESS_ROOTLESSKIT_NET=slirp4netns` and `DOCKERD_ROOTLESS_ROOTLESSKIT_MTU=65520` to the DIND docker-compose example
- The `docker:dind-rootless` base image defaults to vpnkit as the network driver, which has substantially lower throughput than slirp4netns
## The problem
I noticed that pulling containers as well as downloading data within the container when running act_runner as DIND was very slow (see Ookla speedtest results in the following). While analysing the issue, I found that this was caused by the usage of vpnkit.
The `docker:dind-rootless` base image defaults to vpnkit as the network driver. slirp4netns was [added as an opt-in option](https://github.com/docker-library/docker/pull/543 ) and must be explicitly enabled via `DOCKERD_ROOTLESS_ROOTLESSKIT_NET=slirp4netns`.
This means anyone following the current DIND example gets vpnkit, which has significantly lower network throughput. This affects **all** network operations in the container — image pulls, package installs, and CI tasks.
Per the [rootlesskit iperf3 benchmarks](https://github.com/rootless-containers/rootlesskit/blob/master/docs/network.md ):
| Driver | MTU 1500 | MTU 65520 |
|--------|----------|-----------|
| **vpnkit** | 0.60 Gbps | not supported |
| **slirp4netns** | 1.06 Gbps | 7.55 Gbps |
## Real-world benchmark results (Ookla speedtest, same server)
| | Download | Upload |
|---|---|---|
| **Default (vpnkit)** | ~130 Mbps | ~126 Mbps |
| **slirp4netns + MTU 65520** | ~958 Mbps | ~462 Mbps |
## References
- [docker-library/docker#543 ](https://github.com/docker-library/docker/pull/543 ) — added slirp4netns to dind-rootless as opt-in (vpnkit remains default)
- [rootlesskit network docs](https://github.com/rootless-containers/rootlesskit/blob/master/docs/network.md ) — iperf3 benchmarks
---------
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/786
Reviewed-by: silverwind <silverwind@noreply.gitea.com >
Co-authored-by: stecklars <stecklars@noreply.gitea.com >
Co-committed-by: stecklars <stecklars@noreply.gitea.com >
2026-02-16 07:56:45 +00:00
Zettat123
a7080f5457
Update examples for GITEA_RUNNER_REGISTRATION_TOKEN env ( #630 )
...
For https://github.com/go-gitea/gitea/pull/32946
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/630
Reviewed-by: Lunny Xiao <lunny@noreply.gitea.com >
Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com >
Co-authored-by: Zettat123 <zettat123@gmail.com >
Co-committed-by: Zettat123 <zettat123@gmail.com >
2025-01-05 22:25:32 +00:00
Schallbert
b282356e9e
update example for docker-compose to allow fix 502 errors in case Gitea not yet ready on runner startup ( #605 )
...
Minimalistic approach: Only adds what is needed to fix #600
Context: https://blog.schallbert.de/en/fix-gitea-runner/
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/605
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Reviewed-by: Zettat123 <zettat123@noreply.gitea.com >
Co-authored-by: Schallbert <schallbert@mailbox.org >
Co-committed-by: Schallbert <schallbert@mailbox.org >
2024-09-26 05:54:54 +00:00
vilunov and Nikita Vilunov
4c35288175
Add DIND docker-compose example ( #365 )
...
Co-authored-by: Nikita Vilunov <nikita@vilunov.me >
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/365
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: vilunov <vilunov@noreply.gitea.com >
Co-committed-by: vilunov <vilunov@noreply.gitea.com >
2023-10-02 15:12:31 +00:00
m90 and Frederik Ring
10dc6fb60d
Allow reading registration token from file ( #350 )
...
When deploying the runner in a Docker Swarm setup, it can be useful to
read the potentially sensitive token from a secret instead of having to
pass it from an environment variable.
Co-authored-by: Frederik Ring <frederik.ring@gmail.com >
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/350
Reviewed-by: Jason Song <i@wolfogre.com >
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com >
Co-authored-by: m90 <m90@noreply.gitea.com >
Co-committed-by: m90 <m90@noreply.gitea.com >
2023-09-04 04:12:07 +00:00
Chris Cureau and ccureau
a384adbbc6
Documentation enhancements ( #207 )
...
This PR addresses the issue listed in issue #170 regarding how to set up rootless Docker. It also expands on the documentation to show how to create deployments for different environments.
Co-authored-by: ccureau <ccureau@noreply.gitea.io >
Reviewed-on: https://gitea.com/gitea/act_runner/pulls/207
Reviewed-by: Jason Song <i@wolfogre.com >
Co-authored-by: Chris Cureau <cmcureau@gmail.com >
Co-committed-by: Chris Cureau <cmcureau@gmail.com >
2023-06-05 08:46:15 +00:00