Crizomb/SelfHosting
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update VMs/ForgejoRunner/README.md

Browse source
This commit is contained in:
Crizomb 2025-12-25 01:26:09 +01:00
parent e33e131de7
commit 56a019d0fb
1 changed files with 11 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

16
VMs/ForgejoRunner/README.md
View file

@ -1,7 +1,13 @@
# Forgejo runner setup # Forgejo runner setup
Run forgejo runners instance inside a VM to do very dirty things but securely Run forgejo runners instance inside a VM to do very dirty things but securely <br>
forgejo runner run as a docker container inside the VM, and have access to docker socket to create The "dirty things" is just having forgejo running in priviliged container, with direct access to the host (VM) docker socket <br>
docker containers for CI/CD things Runners can easily get full access to host, but the host is a VM so it's ok <br>
I use [incus](https://linuxcontainers.org/incus/) to create the VM. I love it, very simple, docker like interface <br>
See launch_forgejo_runner_vm.sh for more information about the VM setup. <br>
To setup, you still need to enter VM, and follow forgejo [runner instalation guide](https://forgejo.org/docs/next/admin/actions/runner-installation/) <br>
It's still a little bit manual, but it's done in 30s
To setup, you still need to enter VM, and follow forgejo [runner instalation guide] (https://forgejo.org/docs/next/admin/actions/runner-installation/)
And copy paste lof of things