From 56a019d0fbb42de9323bd7ff89497aa0cc6d94cb Mon Sep 17 00:00:00 2001 From: Crizomb Date: Thu, 25 Dec 2025 01:26:09 +0100 Subject: [PATCH] Update VMs/ForgejoRunner/README.md --- VMs/ForgejoRunner/README.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/VMs/ForgejoRunner/README.md b/VMs/ForgejoRunner/README.md index bf451cb..6db7b5b 100644 --- a/VMs/ForgejoRunner/README.md +++ b/VMs/ForgejoRunner/README.md @@ -1,7 +1,13 @@ # Forgejo runner setup -Run forgejo runners instance inside a VM to do very dirty things but securely -forgejo runner run as a docker container inside the VM, and have access to docker socket to create -docker containers for CI/CD things +Run forgejo runners instance inside a VM to do very dirty things but securely
+The "dirty things" is just having forgejo running in priviliged container, with direct access to the host (VM) docker socket
+Runners can easily get full access to host, but the host is a VM so it's ok
+I use [incus](https://linuxcontainers.org/incus/) to create the VM. I love it, very simple, docker like interface
+See launch_forgejo_runner_vm.sh for more information about the VM setup.
-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 + + + +To setup, you still need to enter VM, and follow forgejo [runner instalation guide](https://forgejo.org/docs/next/admin/actions/runner-installation/)
+It's still a little bit manual, but it's done in 30s + \ No newline at end of file