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:27:22 +01:00
parent 56a019d0fb
commit 36ef94c83a
1 changed files with 7 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

15
VMs/ForgejoRunner/README.md
View file

@ -1,13 +1,12 @@
# Forgejo runner setup # Forgejo runner setup
Run forgejo runners instance inside a VM to do very dirty things but securely <br>
The "dirty things" is just having forgejo running in priviliged container, with direct access to the host (VM) docker socket <br> Run forgejo runners instance inside a VM to do very dirty things but securely. <br><br>
Runners can easily get full access to host, but the host is a VM so it's ok <br> The "dirty things" is just having forgejo running in priviliged container, with direct access to the host (VM) docker socket. <br><br>
I use [incus](https://linuxcontainers.org/incus/) to create the VM. I love it, very simple, docker like interface <br> Runners can easily get full access to host, but the host is a VM so it's ok <br><br>
See launch_forgejo_runner_vm.sh for more information about the VM setup. <br> I use [incus](https://linuxcontainers.org/incus/) to create the VM. I love it, very simple, docker like interface <br><br>
See launch_forgejo_runner_vm.sh for more information about the VM setup. <br><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><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 It's still a little bit manual, but it's done in 30s