Compatibility with AlpineLinux #34
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: forgejo/runner#34
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We've tried to use the forgejo runner (act) on a Host with AlpineLinux, which failed miserably :(
It seems that the lxc-Scripts (
start-lxc.sh
,lxc-helpers.sh
andlxc-helpers-lib.sh
) created in the~/.cache/act
folder are highly coupled to a hostsystem with systemd and a full fledged Ubuntu/Debian. Further, busybox is also not supported (which comes with AlpineLinux).Is there a way to run the runner on AlpineLinux? And if not, is there a way to run it in docker, but run commands on the hostsystem itself?
If both is not an option, what are the steps required to get the runner running on AlpineLinux? Just the 3 scripts or is there more involved?
LXC support is still incomplete and tied to Debian bullseye. If running in a container is good enough for your needs, I would suggest using an Alpine docker image.
A label such as
alpine:docker://alpine:latest
should provide you that.Alternatively, if you're ready to try and patch the runner, there is an LXC template for alpine. But that's more work.
Did you figure something out?
No.
We use a RaspberryPi with Ubuntu + Wireguard to run the runner now.
I know, this is not the solution for the core problem here, but we needed a quick solution.
AlpineLinux compatibility would still be awesome.
If I got some free time, I will dig into this.