Package Details: act-runner-bin 0.2.11-1

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)

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):

cd /etc/act_runner
sudo -u act_runner act_runner register --config /etc/act_runner/act_runner.yaml

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:

:: Downloading PKGBUILDs...
 (1/1) act-runner-bin-0.2.6-3                       [----------------------]

error: failed to parse srcinfo for 'act-runner-bin-0.2.6-3': undeclared architecture 'aarch64' in key 'source_aarch64': Line 20: source_aarch64 = https://gitea.com/gitea/act_runner/releases/download/v0.2.6/act_runner-0.2.6-linux-arm64.xz

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:

# Maintainer: Manuel Gugger <mdgdot[at]tutanota[dot]com>

pkgname=act-runner-bin
pkgver=0.2.6
pkgrel=2
pkgdesc="A runner for Gitea Actions based on GitHub's Act"
arch=('aarch64')
url="https://gitea.com/gitea/act_runner"
license=('MIT')
optdepends=('docker: for running containers')
provides=('act_runner')
conflicts=('act_runner')

source_aarch64=("https://gitea.com/gitea/act_runner/releases/download/v${pkgver}/act_runner-${pkgver}-linux-arm64.xz")
sha256sums_aarch64=('SKIP')

source=('act_runner.service'
        'act_runner.yaml'
        'act_runner.sysusers'
        'act_runner.tmpfiles')
sha256sums=('SKIP'
            'SKIP'
            'SKIP'
            'SKIP')

package() {
    mv act_runner-${pkgver}-linux-arm64 act_runner
    install -Dm755 act_runner -t "$pkgdir/usr/bin"
    install -Dm644 "$srcdir/act_runner.service" "$pkgdir/usr/lib/systemd/system/act_runner.service"
    install -Dm644 "$srcdir/act_runner.yaml" "$pkgdir/etc/act_runner/act_runner.yaml"
    install -Dm644 "$srcdir/act_runner.sysusers" "$pkgdir/usr/lib/sysusers.d/act_runner.conf"
    install -Dm644 "$srcdir/act_runner.tmpfiles" "$pkgdir/usr/lib/tmpfiles.d/act_runner.conf" 

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:

  1. register the runner with gitea instance, by running act_runner register --config /etc/act_runner/act_runner.yaml at /var/lib/act_runner. Make sure the file is accessible by act_runner user (just chown to the user).
  2. add act_runner to docker 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"