Linux Articles

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.

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.

Hand-writing Quadlet files works for one host. For a fleet, the containers.podman collection’s native Quadlet generation lets you describe containers as Ansible state, including secrets, registry logins, and templated configuration. A small Mastodon welcome bot makes a concrete example.

My ThinkPad T14s shipped with an Intel XMM7560 LTE modem that would not register on the network until Lenovo’s proprietary FCC-unlock helper ran. I replaced it with a roughly 100-line bash script from a ModemManager merge request, and along the way learned that the “unlock” is just a small challenge-response handshake that is easy to explain in plain shell.

An opinionated production-ops guide to Podman on Linux servers - why I prefer it over Docker, how Quadlets replace Compose files, and practical patterns from real deployments including secrets management, auto-updates, and Docker compatibility.