Fork 0
Go to file
Tomasz Duda b0bd503b11 add token support for exec (#247)
allow to pass token from secrets

Reviewed-on: gitea/act_runner#247
Reviewed-by: Jason Song <i@wolfogre.com>
Reviewed-by: Lunny Xiao <xiaolunwen@gmail.com>
Co-authored-by: Tomasz Duda <tomaszduda23@gmail.com>
Co-committed-by: Tomasz Duda <tomaszduda23@gmail.com>
2023-06-20 08:41:22 +00:00
.gitea/workflows Build docker image `gitea/act_runner/x.y.z-dind-rootless` (#239) 2023-06-15 05:27:35 +00:00
examples Build docker image `gitea/act_runner/x.y.z-dind-rootless` (#239) 2023-06-15 05:27:35 +00:00
internal add token support for exec (#247) 2023-06-20 08:41:22 +00:00
scripts Improve `run.sh` to handle empty labels and log to stdout (#237) 2023-06-13 04:09:11 +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 build: improve compression and update GitHub actions (#168) 2023-05-01 21:59:43 +08:00
.golangci.yml chore: add .golangci config 2022-11-24 15:36:28 +08: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
Dockerfile implement act_runner rootless image (#208) 2023-06-12 06:35:27 +00:00
Dockerfile.rootless implement act_runner rootless image (#208) 2023-06-12 06:35:27 +00:00
LICENSE Add license 2022-11-24 15:36:16 +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 Documentation enhancements (#207) 2023-06-05 08:46:15 +00:00
build.go Support cache (#25) 2023-02-28 23:39:30 +08:00
go.mod Upgrade act (#248) 2023-06-20 08:33:42 +00:00
go.sum Upgrade act (#248) 2023-06-20 08:33:42 +00:00
main.go Refactor to new framework (#98) 2023-04-04 21:32:04 +08: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



./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-20.04:docker://node:16-bullseye,ubuntu-18.04:docker://node:16-buster,linux_arm:host):

INFO Registering runner, name=Test.local, instance=, labels=[ubuntu-latest:docker://node:16-bullseye ubuntu-22.04:docker://node:16-bullseye ubuntu-20.04:docker://node:16-bullseye ubuntu-18.04:docker://node:16-buster].
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


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

Example Deployments

Check out the examples directory for sample deployment types.