Search Criteria
Package Details: act-runner-bin 0.2.11-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/act-runner-bin.git (read-only, click to copy) |
---|---|
Package Base: | act-runner-bin |
Description: | A runner for Gitea Actions based on GitHub's Act |
Upstream URL: | https://gitea.com/gitea/act_runner |
Licenses: | MIT |
Conflicts: | act_runner |
Provides: | act_runner |
Submitter: | manolito |
Maintainer: | manolito |
Last Packager: | manolito |
Votes: | 1 |
Popularity: | 0.000788 |
First Submitted: | 2023-07-27 15:12 (UTC) |
Last Updated: | 2024-09-30 12:43 (UTC) |
Dependencies (1)
- docker (rancher-desktop-gitAUR, docker-gitAUR, podman-docker-gitAUR, rancher-desktopAUR, docker-cli-binAUR, podman-docker) (optional) – for running containers
Latest Comments
manolito commented on 2024-04-09 10:11 (UTC)
updated to 0.2.9, the act_runner user gets now added to the docker group automatically and looks for a .runner file in /etc/act_runner. Docker group is not required if you use the label "self-hosted" during registration.
To register the runner (create the .runner in /etc/act_runner):
manolito commented on 2024-03-26 13:01 (UTC)
Thanks for the hint and apologies, I forgot to update the .SRCINFO. It's fixed now.
AlexBocken commented on 2024-03-21 18:57 (UTC) (edited on 2024-03-21 18:58 (UTC) by AlexBocken)
I think the aarch64 addition has messed something up:
manolito commented on 2024-03-04 09:06 (UTC)
hi @madskjeldgaard
thanks for the input. I've added the aarch64 as a supported architecture.
Let me know if that change works for you as I don't have an aarch64 device at the moment.
madskjeldgaard commented on 2024-02-28 20:37 (UTC) (edited on 2024-02-28 20:37 (UTC) by madskjeldgaard)
Hi! It would be great if you could add support for aarch64 in this as well.
The binaries are available from the same repo with arm64 instead of amd64 as the arch.
I tested it now and it works here. I called paru -G act-runner-bin and then modified the file to look like this:
wutipong commented on 2024-02-15 20:10 (UTC) (edited on 2024-02-15 20:11 (UTC) by wutipong)
I think you might want to add how to set up the service, probably in the wiki page.
Basically I have to do the following before the service can start:
act_runner register --config /etc/act_runner/act_runner.yaml
at/var/lib/act_runner
. Make sure the file is accessible byact_runner
user (just chown to the user).act_runner
todocker
group since this relies on docker.manolito commented on 2024-02-15 14:43 (UTC)
thanks for your input!
I've adapted the package to use its own act_runner user instead of root and it will use /var/lib/act_runner as HOME-env.
The .runner file should still go in /etc/act_runner.
ksj commented on 2024-02-13 15:12 (UTC)
In systemd service is missing
Environment="HOME=/root/"
Otherwise it will fail with
bash: .cache/act/180b39b7a2ede212/act/workflow/0.sh: No such file or directory
When you try workflow in project in gitea. Use "WorkingDirectory=" doesn't work.Also attached act_runner.yaml is older than latest config - generated with "act_runner generate-config"