<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Forgejo on Adam Guderski</title><link>https://guder.ski/tags/forgejo/</link><description>Recent content in Forgejo on Adam Guderski</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://guder.ski/tags/forgejo/index.xml" rel="self" type="application/rss+xml"/><item><title>Building Docker images with Forgejo Actions</title><link>https://guder.ski/posts/forgejo-docker-builds/</link><pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate><guid>https://guder.ski/posts/forgejo-docker-builds/</guid><description>&lt;p&gt;Lately I was looking for a Docker registry that I could host locally and keep couple of images that I run on multiple hosts. I didn&amp;rsquo;t want to run a bare &lt;a href="https://hub.docker.com/_/registry" target="_blank" rel="noopener noreferrer"&gt;registry&lt;/a&gt;&#10; but something more complete and I settled on a Forgejo instance which will also make me able to keep Dockerfiles and use it&amp;rsquo;s integrated CI to build the images.&lt;/p&gt;&#10;&lt;p&gt;Forgejo&amp;rsquo;s CI is based on GitHub Actions (unfortunately - I&amp;rsquo;d love to see an option to use GitLab CI workflow and syntax instead) so it&amp;rsquo;s easy to find workflows that can be adapted for your needs. The setup of a runner is not that straightforward, though - Forgejo&amp;rsquo;s docs are a bit vague so I&amp;rsquo;ll present a minimal configuration that I got to work properly. For security reasons, I chose to build images with &lt;a href="https://buildah.io/" target="_blank" rel="noopener noreferrer"&gt;buildah&lt;/a&gt;&#10; since &lt;a href="https://github.com/GoogleContainerTools/kaniko/issues/3348" target="_blank" rel="noopener noreferrer"&gt;kaniko is no longer maintained&lt;/a&gt;&#10;.&lt;/p&gt;</description></item></channel></rss>