forgejo/infrastructure-documentation
1
0
Fork 0
mirror of https://code.forgejo.org/infrastructure/documentation synced 2024-12-21 20:53:51 +00:00
Code Issues Activity

Forgejo runner require libvirt capabilities for LXC

Browse source
This commit is contained in:
Earl Warren 2024-11-28 09:22:56 +00:00
parent ab4fffb3c3
commit 80180a4b2a
No known key found for this signature in database
GPG key ID: 0579CB2928A78A00
2 changed files with 15 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
lxc.md
View file

@ -60,6 +60,20 @@ lxc-helpers.sh lxc_install_lxc $name $ipv4 $ipv6
lxc-helpers.sh lxc_container_user_install $name $(id -u) $USER
```
### Docker, LXC and libvirt
```sh
name=forgejo-host
ipv4=10.85.12
ipv6=fc33
lxc-helpers.sh lxc_container_create --config "docker lxc libvirt" $name
echo "lxc.start.auto = 1" | sudo tee -a /var/lib/lxc/$name/config
lxc-helpers.sh lxc_container_start $name
lxc-helpers.sh lxc_install_docker $name
lxc-helpers.sh lxc_install_lxc $name $ipv4 $ipv6
lxc-helpers.sh lxc_container_user_install $name $(id -u) $USER
```
## Hetzner
All hardware machines are running Debian GNU/linux bookworm. They are LXC hosts

2
runner-lxc.md
View file

@ -3,7 +3,7 @@
The LXC container in which the runner is installed must have capabilities that support the backend.
- docker:// needs a Docker enabled container
- lxc:// needs a Docker and LXC enabled container
- lxc:// needs a Docker, LXC and libvirt enabled container
The runners it contains are not started at boot, it must be done manually. The bash history has the command line to do so.