Maintaining A Fedora IoT Remix And It's Actually Fun!

Let me introduce you to the amazing topic of building and maintaining your own Fedora IoT OS/Firmware Remix.

I want to use Fedora IoT on Raspberry Pi (and a multitude of other devices), but not without my own customizations, scripts and all that flavour. So I set out on an adventure to build and maintain a custom variant of Fedora IoT, a so-called Remix, because it’s a great system and surprisingly fitted to be customized.

I’m In Need For Some Remix

I’m currently in need for a solid firmware operating system based on linux with some very specific requirements - both for my work and all the Raspberry Pis in my possession. Based on the work of a friend and former colleague of mine1 and his research as part of his bachelor thesis I came to a quite opinionated solution based on Fedora IoT.

Fedora IoT has some nifty features:

With tools such as RPM-OSTree, Gitlab, Gitlab CI, Gitlab-Runner, EC2, Shell-Scripting, Containers, NGINX and so on we’ll look into how to build and maintain a Remix of Fedora IoT. But let’s not get ahead of ourselves.

The Journey Ahead

What I want as a start is placing my own shell-scripts, systemd units, configurations and RPMs onto multiple devices, let’s say all my Raspberry Pis. So coming from stock Fedora IoT a base requirement is to ship my own RPM-OSTree remote since that’s the source this system is receiving it’s updates from. OSTree allows to specify different remotes and switch freely between them and their respective branches and/or commits. So after we’ve setup a repo we can use the rpm-ostree command with e.g. rpm-ostree rebase myremote:mystuff/stable/aarch64 on the Fedora IoT host to switch over to our own repo, branch and architecture.

I figure the first thing and most interesting one to look at is building custom OSTree commits on top of stock Fedora IoT to fill our remote with some life. The sources for those custom commits come from a git repository which is not to be confused with an OSTree repository. After that we can take a look at how to serve this OSTree repository we just built, either openly or behind some authentication mechanism like mTLS. With the foundation setup and the basics clear we can move forward to bring some automagic into play and use CI to build new stuff for new source commits. While automating the build process is quite nice on it’s own, this should definitely happen on our existing OSTree repository and also update it with the result instead of creating a new repo every time. So we’ll spent some time on bringing the remote repo into the CI.

While all of the things above can be done in a multitude of ways I’ll give you my approach as one of many possibilities and hope you’ll find your own way together with the utter excitement of this topic. ~amazing


  1. Checkout his blog: 

Any thoughts of your own?

Feel free to raise a discussion with me on Mastodon or drop me an email.


The text of this post is licensed under the Attribution 4.0 International License (CC BY 4.0). You may Share or Adapt given the appropriate Credit.

Any source code in this post is licensed under the MIT license.