Gitea Actions without Docker-in-Docker: every job a pod, every build on BuildKit

Sun, 08 Nov 2026 10:00:00 +0100

Back in 2020 I wrote about all the parts required for a self-hosted continuous integration: Gitea for the code, Drone for the builds, a registry for the images. Drone is long gone. Since December 2023 my builds have run on Gitea Actions, and the runner moved into the cluster on the same day as Gitea itself. Like almost every runner setup you find online, mine was a StatefulSet with two containers per pod: the runner, and a privileged docker:dind sidecar that actually ran the jobs.

Caching on johanneskueber.com

Gitea Actions without Docker-in-Docker: every job a pod, every build on BuildKit