runner

Author	SHA1	Message	Date
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
Earl Warren	0232fe1255	fix: forgejo-runner-service.sh config.yml must point to the cache It is not the default $HOME/.cache/actcache and must be set in config.yml otherwise it won't be used.	2025-01-27 12:39:58 +01:00
Earl Warren	253eb51687	fix: forgejo-runner-service.sh misses LXC config When re-creating the LXC container, the INPUTS_LXC_CONFIG must be set otherwise it will always use the default.	2025-01-27 10:00:51 +01:00
Earl Warren	5f92ffdbc6	feat: systemd unit example for managing LXC containers (#451 ) Refs: https://code.forgejo.org/forgejo/runner/issues/450 Reviewed-on: https://code.forgejo.org/forgejo/runner/pulls/451 Reviewed-by: Michael Kriese <michael.kriese@gmx.de> Co-authored-by: Earl Warren <contact@earl-warren.org> Co-committed-by: Earl Warren <contact@earl-warren.org>	2025-01-25 12:24:31 +00:00