AstraLuma1d ago

I spent the last week or two configuring a CI/CD runner for #TeahouseHosting on #Codeberg, here's how I did it.

https://qwertyuiop.ninja/2026/03/16/codeberg-runner.html

I wasn't really finding in-depth documentation and blog posts, and in particular none of the published examples would build container images--the biggest limitation of Codeberg's offering.

So I fixed it.

#Forgejo

Run a Runner on Codeberg

So you wanna make the jump to Codeberg, but aren’t happy with their CI? Here’s how to run your own!

qwertyuiop.ninja
Show threadAstraLuma

It even includes a few cursed ops suggestions:

* Triple Docker: One standard one for the runner daemon, one for the runner to run jobs in, and one for jobs to use
* Docker state on tmpfs on zram

Mar 17 at 3:39amWeb
Show threadAstraLuma1d ago
I do kinda want to do the triple docker, or even per-job docker, but getting that dialed is going to be annoying.
Show threada holosprite ​1d ago
@astraluma
> Docker state on tmpfs on zram
Show threadAstraLuma1d ago
@ratsprite I have gotten very flexible with containers
Show threada holosprite ​1d ago
@astraluma you really have, I keep bouncing off them every six months or so, but with 32GB sitting in my home server this is tempting (I'm nowhere near needing to set up my own CI, but...)
Show threada holosprite ​1d ago
@astraluma DDR3, bless its socks
Show threadAstraLuma1d ago

@ratsprite it's unfortunately half required if you're doing serious development on codeberg.

Thankfully, it turns out the system requirements for doing so are real small