+++
title = 'Possible solution for self-hosting Bluebuild images without CI'
date = 2025-09-14
tags = ['selfhosting', 'bluebuild', 'ublue', 'fedora', 'containers', 'bootc']
+++

As an anti-Big Tech self-hoster, I don't like using GitHub to build and store my Ublue/Bluebuild container images.

I'm thinking of doing the building on my own machine and pushing the image to a self-hosted container registry. The [bluebuild cli](https://github.com/blue-build/cli) makes this easier. For a self-hosted container registry I can use [Harbor](https://goharbor.io/).

I would write a script that fetches the latest version from my Codeberg repo, runs something like `bluebuild build -v --push --registry $HARBOR_REGISTRY recipes/recipe.yml` locally, and sends the log output to a file for debugging purposes.

I would have the script run as a systemd service with a daily timer. If I use a systemd service then I wouldn't necessarily have to store the log output to a file, as I could view it with `journalctl -xeu bluebuild-build.service`, but it might be nice to have separate log files in addition to that.

This way I can self-host it without having to fiddle with Gitea or Codeberg CI.