actions
/
runner
mirror of https://code.forgejo.org/forgejo/runner
1
0
Fork 0
Code Packages
runner/examples
History
Earl Warren b79578d98e
feat: forgejo-runner-service.sh safeguard to avoid overheating 
re-creating the LXC container from scratch is expensive. When
rebooting or when multiple units start at the same time, it may cause
an execessive load.

Use a global lock to guard this operation so they happen in sequence
and not in parallel. They typically take around one minute to complete
which means that in the event of a reboot, it will take around 1
minutes * the number of runners for the unlucky one to start.

During this interval workflows will have to wait.
 		2025-01-27 14:23:58 +01:00
..
docker fix: example uses code.forgejo.org/oci 2025-01-15 12:24:32 +01:00
docker-compose fix: example uses code.forgejo.org/oci 2025-01-15 12:24:32 +01:00
kubernetes fix: example uses code.forgejo.org/oci 2025-01-15 12:24:32 +01:00
lxc-systemd feat: forgejo-runner-service.sh safeguard to avoid overheating 2025-01-27 14:23:58 +01:00
README.md feat: systemd unit example for managing LXC containers (#451) 2025-01-25 12:24:31 +00:00

README.md

This directory contains a collection of usage and deployment examples.

Workflow examples can be found in the documentation.

Section Description
docker using the host docker server by mounting the socket
LXC systemd systemd unit managing LXC containers dedicated to a single runner
docker-compose all in one docker-compose with the Forgejo server, the runner and docker in docker
kubernetes a sample deployment for the Forgejo runner