Coming from a Debian-based Linux background, using the Ubuntu base image for my Docker containers was a natural choice. However, the overhead, even on the impressively-slimmed Hub images, was hard to justify. Seeking to create images that were "just right" in size, without unused packages or dependencies, I made the switch to Alpine.

Alpine's modified BusyBox has a surprising amount of functionality, and the package repository contains plenty of muslc-safe versions of commonly-used packages. It's been a valuable exercise in doing more with less, and, as Alpine is keen to point out, an image with fewer packages makes for a more sustainable environment with a smaller attack surface.

My only regret is that Alpine's documentation leaves a lot to be desired.

I have used libvirt in every Linux hypervisor deployment I do. I frequently deploy RHEL or CentOS hypervisor servers with libvirt as the VMM of choice. It's installable via the guided setup for EL-based Linux distros, it uses minimal resources and overhead, integrates seamlessly with KVM and Qemu, and provides powerful CLI for advanced users and experts looking for automated deployments, or via VirtManager in your favorite Linux desktop environment. Best used with Linux VMs, it allows KVM and QEMU direct hardware virtualization access.

Using Arch Linux for our systems and servers means getting the latest technology and fixes early, as well as early warnings for potential future breakage in other (slower) distributions. It's been easy to maintain, easy to automate, and most importantly: easy to debug.

While our software target is every recent Linux distribution, using Arch internally ensured that everyone understands the full system without any knowledge gaps.

Global familiarity, free, widely used, and as a debian distro feels more comfortable when rapidly switching between local macOS and remote command lines.

CentOS does boast quite a few security/stability improvements, however as a RHEL-based distro, differs quite significantly in the command line and suffers from slightly less frequent package updates. (Could be a good or bad thing depending on your use-case and if it is public facing)