Larvitz Blog
Mastodon

Welcome to Larvitz Blog! I’m Christian, a Cloud Consultant by day and FreeBSD enthusiast by night, with over 20 years in enterprise IT. Here I write about FreeBSD jails, PF firewalling, self-hosting, Linux system administration, and anything that’s cleanly engineered. Most articles are hands-on guides born from running my own infrastructure, from dual-stack networking and Ansible automation to hosting a Mastodon instance on FreeBSD.

Have a question or want to discuss something? Find me on the Fediverse at @Larvitz@burningboard.net. I’m always happy to chat!

Linux Articles

Fedora Hummingbird: Distroless, Container-Native Linux and a Slim mastogreet

Fedora Hummingbird brings the distroless container model to a full, image-based rolling operating system, and it ships a catalog of hardened language images alongside it. I rebuild the mastogreet bot’s Containerfile on top of registry.access.redhat.com/hi/python to see what changes, what shrinks, and where the commercial Red Hat Hardened Images downstream fits in.

Red Hat Offline Knowledge Portal: All the Docs, Air-Gapped, On Your Laptop

The entire Red Hat documentation site and the full Knowledgebase fit into a single OCI container that updates weekly, runs locally with a web UI and Solr search, and is included in every RHEL subscription that bundles Satellite. I have it on my laptop. I use it daily. Almost nobody I talk to knows it exists. This post is my small contribution to fixing that.

Distrobox: Different Distributions in a Box, Powered by Podman

A “real” RHEL container on a Fedora laptop, an Arch box for the AUR, an Ubuntu box for that one vendor tool that ships .deb files only, all of them with your home directory mounted, your shell history shared, and GUI apps that integrate into your desktop as if they were native. Distrobox uses Podman to make that boring instead of clever, and it pairs especially well with Atomic distributions where the host is meant to stay immutable.

Reproducible Ansible with Execution Environments

A “control node” with a hand-curated venv works. Until it doesn’t. A colleague has different collection versions, CI installs a slightly newer Python library, and a playbook that ran yesterday now fails. Execution Environments turn the control node into a versioned container image. ansible-builder produces it, ansible-navigator runs against it, and the same artifact ships from your laptop into AAP/AWX without modification.