Forgejo

330 readers

1 users here now

This is a community dedicated to Forgejo.

Useful links:

Rules:

Posts must be relevant to Forgejo
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s ok to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

founded 2 years ago

MODERATORS

alx@programming.dev

Better Forgejo Action Runners config (lemmy.world)

submitted 1 month ago by chaospatterns@lemmy.world to c/forgejo@programming.dev

2 comments fedilink hide all child comments

I have Forgejo working pretty well. I also have a Forgejo runner running workflows successfully using a Docker-in-Docker system running in Kubernetes. This works pretty well and I like it, but I'm starting to run into some challenges with more advanced workflow use-cases.

For example, I only have one runner so jobs stack up. I wasn't sure how to implement multiple runners given that each runner needs to save a static token. I saw some references to ephemeral runners. Does anybody use auto-scaling or multiple-instances such as with ephemeral runners?

Additionally, using docker-in-docker has some issues. The Docker daemon gets persisted across jobs so the output images stack up and I have to periodically run docker system prune inside the runner. Trying to run docker commands that require logging in inside the workflow also conflicts with Forgejo's own control of the Docker Daemon.

Does anybody else run into these kinds of issues and have a good strategy? There was this issue about using firecracker micro-vms which could have fixed the d-in-d issues, but no recent updates.

you are viewing a single comment's thread
view the rest of the comments

[–] moonpiedumplings@programming.dev 2 points 3 weeks ago (1 children)

Finally found this post after a few minutes of searching:

I came across this: https://github.com/cloudbase/garm , which is gitea (probably compatible with forgejo) actions using Incus containers/virtual machines, or on kubernetes directly.

It looks like it's possible to create an alternate implementation of the forgejo actions runner, which doesn't uses different methods of execution.

[–] chaospatterns@lemmy.world 1 points 2 weeks ago

Nice share. I'll look into it more and try it out. Thanks.