Ran containers on Podman and Quadlet
Deployed a container plane on Podman and Quadlet under systemd
rather than Docker, because Docker's default bridge‑port publishing
can bypass UFW rules — and gave deploys an unprivileged user with
one fixed command instead of root.
September 2026

Situation. The platform needed somewhere to run application
containers. The obvious choice was the industry default, and the
obvious choice was wrong for this host in a specific way: it
rewrites the kernel's packet‑filter rules and publishes container
ports above the firewall rules the hardening role installs, so a
container quietly becomes reachable from the internet regardless of
what the firewall was told.

Task. A container plane had to be chosen that does not bypass the
firewall, does not add a second supervisor beside the one already
trusted, and does not require a person to be root to ship a release.

Action. The plane is a daemonless container engine driving units
generated by the operating system's own supervisor. There is no
second process manager: containers are services, they start the way
services start, and they are described in the same declarative form
as everything else. The containers use host networking with no
published ports at all, which removes the firewall‑bypass question
rather than mitigating it. Units run at the system level rather than
rootless, and that is recorded as a trade — it keeps the automation
simple and normal, at the cost of the stricter isolation rootless
would give, and the note says which way to move if container escape
ever matters more than automation simplicity. Deployment was
separated from provisioning: root sets up the deployment path once,
and thereafter an unprivileged user redeploys by running one fixed
script through a scoped rule that permits that command and no
arguments. Build the image, restart the service. No root shell, no
arbitrary commands.

Result. Containers run under the supervisor that was already
trusted, behind the firewall that was already declared, and a
routine release uses one scoped command without a root shell. The
choice against the default is written down with its reason, which
matters more than the choice — the next person will be told to use
the default by every article they read.

Categories:
1DevOps	/categories/devops/	engineer.company	70
1Infrastructure	/categories/infrastructure/	engineer.company	70
1Containers (Docker/Kubernetes)	/categories/containers/	engineer.company	70
1Automation & CI/CD	/categories/automation/	engineer.company	70
1Linux & Servers	/categories/linux/	engineer.company	70
1Security	/categories/security/	engineer.company	70

Services:
1Cloud Infrastructure & Migration	/services/cloud-infrastructure/	engineer.company	70
1DevOps & CI/CD Automation	/services/devops-cicd/	engineer.company	70
1Containerization & Orchestration	/services/containerization/	engineer.company	70
1Security & Access Management	/services/security-access/	engineer.company	70

hThis page on the web	URL:https://engineer.company/portfolio/ran-containers-on-podman-and-quadlet/	engineer.company	70
