A runner for Gitea based on act.
Go to file
2024-05-01 16:35:34 -05:00
.gitea/workflows Release nightly versions for tags (#536) 2024-04-10 07:06:08 +00:00
examples Add DIND docker-compose example (#365) 2023-10-02 15:12:31 +00:00
internal fix: lint 2024-05-01 16:35:34 -05:00
scripts fix: Exit docker container on any process exit (#462) 2024-01-30 13:47:42 +00:00
.editorconfig Add .editorconfig and .gitattributes (#186) 2023-05-13 23:51:22 +08:00
.gitattributes Add .editorconfig and .gitattributes (#186) 2023-05-13 23:51:22 +08:00
.gitignore Bump act to v0.259.0 (#491) 2024-03-03 16:34:37 +00:00
.golangci.yml ci(lint): refactor code for clarity and linting compliance (#289) 2023-07-13 01:10:54 +00:00
.goreleaser.checksum.sh checksum and compress 2023-03-18 01:58:21 -04:00
.goreleaser.yaml ci: improve release process and test robustness (#173) 2023-05-04 09:41:22 +08:00
build.go Support cache (#25) 2023-02-28 23:39:30 +08:00
Dockerfile Upgrade Go to 1.21 and bump other dependencies (#330) 2023-08-10 01:45:25 +00:00
Dockerfile.rootless Update to go1.21 in Dockerfile.rootless (#332) 2023-08-12 00:37:08 +00:00
go.mod Upgrade dependencies (#537) 2024-04-11 04:36:00 +00:00
go.sum Upgrade dependencies (#537) 2024-04-11 04:36:00 +00:00
LICENSE Add license 2022-11-24 15:36:16 +08:00
main.go Refactor to new framework (#98) 2023-04-04 21:32:04 +08:00
Makefile Build docker image gitea/act_runner/x.y.z-dind-rootless (#239) 2023-06-15 05:27:35 +00:00
README.md Use gitea/runner-images by default (#529) 2024-04-02 07:38:14 +00:00
renovate.json5 Add renovate config (#408) 2023-11-23 20:41:10 +00:00

act runner

Act runner is a runner for Gitea based on Gitea fork of act.



Docker Engine Community version is required for docker mode. To install Docker CE, follow the official install instructions.

Download pre-built binary

Visit here and download the right version for your platform.

Build from source

make build

Build a docker image

make docker


Actions are disabled by default, so you need to add the following to the configuration file of your Gitea instance to enable it:



./act_runner register

And you will be asked to input:

  1. Gitea instance URL, like You should use your gitea instance ROOT_URL as the instance argument and you should not use localhost or as instance IP;
  2. Runner token, you can get it from;
  3. Runner name, you can just leave it blank;
  4. Runner labels, you can just leave it blank.

The process looks like:

INFO Registering runner, arch=amd64, os=darwin, version=0.1.5.
WARN Runner in user-mode.
INFO Enter the Gitea instance URL (for example, https://gitea.com/):
INFO Enter the runner token:
INFO Enter the runner name (if set empty, use hostname: Test.local):

INFO Enter the runner labels, leave blank to use the default labels (comma-separated, for example, ubuntu-latest:docker://gitea/runner-images:ubuntu-latest):

INFO Registering runner, name=Test.local, instance=, labels=[ubuntu-latest:docker://gitea/runner-images:ubuntu-latest ubuntu-22.04:docker://gitea/runner-images:ubuntu-22.04 ubuntu-20.04:docker://gitea/runner-images:ubuntu-20.04].
DEBU Successfully pinged the Gitea instance server
INFO Runner registered successfully.

You can also register with command line arguments.

./act_runner register --instance --token <my_runner_token> --no-interactive

If the registry succeed, it will run immediately. Next time, you could run the runner directly.


./act_runner daemon

Run with docker

docker run -e GITEA_INSTANCE_URL=https://your_gitea.com -e GITEA_RUNNER_REGISTRATION_TOKEN=<your_token> -v /var/run/docker.sock:/var/run/docker.sock --name my_runner gitea/act_runner:nightly


You can also configure the runner with a configuration file. The configuration file is a YAML file, you can generate a sample configuration file with ./act_runner generate-config.

./act_runner generate-config > config.yaml

You can specify the configuration file path with -c/--config argument.

./act_runner -c config.yaml register # register with config file
./act_runner -c config.yaml daemon # run with config file

You can read the latest version of the configuration file online at config.example.yaml.

Example Deployments

Check out the examples directory for sample deployment types.