Hacker News Reader

Yeah. MicroVMs make hosting runners pretty straightforward. I had codex make a forgejo runner controller which pulls forgejo actions and creates kubernetes jobs for them.

It was a bit of a pain to configure firecracker with k3s.

It really can’t be understated how much easier hosting CI is with microvms as the security boundary.

View on HN

Agree. I'm always surprised Github still uses huge fat VMs. I imagine this is one of the things that make it much painful at scale. The tricky part with microvms are getting them to run cross-platform. We use an awesome project called smolvm that builds on libkrun and makes this alot easier. As an aside, how have forgejo actions worked for you in practice?

Any other recommendations for microvm ? Need to mess around with them again. Always seemed like the future

If you want something cross-platform, smolvm or microsandbox are great options(built on top of libkrun vmm)! If you are looking for linux-only, the typical choices are firecracker-based solutions.

Re Forgejo actions, I'm just toying around.

Their v15 release (apr 16) really enabled k8s native runners. They added an ephemeral runner API and a bunch of APIs to get jobs. That's what im using to do k8s autoscaling

Reply on news.ycombinator.com