New Forgejo Runner #106
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
renovate
waiting on upstream
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
CCCHH/ansible-infra!106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "new_forgejo_runner"
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?
Moving the Forgejo Runner to Ansible.
Includes some preliminary work for gVisor as well, but the runner is running standard Docker for now as gVisor still needs some upstream fixes.
New Forgejo Runnerto WIP: New Forgejo Runnerfdd9eadad1a4f1f9b9fea4f1f9b9feedd1984517WIP: New Forgejo Runnerto New Forgejo Runner@ -0,0 +14,4 @@labels:# https://forgejo.org/docs/latest/admin/actions/configuration/#choosing-labels- docker:docker://docker.io/library/node:ltsIf we can add these, this replaces the old VM-based runner (almost) completely. Note: this requires a bit of disk space, the ubuntu image is ~15GB.
Sure, can add those!
It's still running on Docker tho, so advanced capabilities like
qemuaren't available, but now that @lilly moved the image builds to Container-based Actions that should be fine.Guess question would be, if we really need the full-sized images (extracted 60GB disk space usage) or if the act versions are fine for us (which are the same that Codeberg use).
https://github.com/catthehacker/docker_images
@ -0,0 +1,9 @@# resolv.conf pointing to Quad9 for bind-mounting into containers on user-defined bridges and using the gVisor runsc runtime.# Example: docker run --runtime runsc --mount type=bind,src=/etc/gvisor-helper-resolv.conf,dst=/etc/resolv.conf,ro=true --network your-user-defined-network -it --rm docker.io/library/debian /bin/bashnameserver 9.9.9.9Why quad 9 and not one of our resolvers?
Would do that once we have proper resolvers we run ourself. This isn't the case right now afaik.
edd1984517ab4e32f461View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.