// learn · linux · rhcsa · 10 min

Podman containers.

Podman is RHEL's container engine — drop-in compatible with the docker CLI, but daemonless and rootless by default. Watch a container go from `podman run` to a persistent systemd unit via Quadlet, the modern way to make rootless services survive reboots.

Podman containers animated tutorial. Daemonless and rootless containers, podman pull/run/exec/logs/ps/inspect, volumes and port publishing, the difference from Docker, and persisting containers as systemd units with Quadlet. RHCSA EX200 ready.
// podman containers

Daemonless, rootless, and Docker-CLI compatible. Watch a container go from pull → run → exec → persistent systemd unit (Quadlet).

// before you start
you should know
  • ·Vague familiarity with containers / Docker
  • ·The systemd-targets / units lesson
  • ·Comfortable running commands as a normal user
by the end you'll

Pull, run, exec, log into containers; mount volumes correctly on SELinux; understand rootless mode; persist with Quadlet.

pace: 10 minutes

podman — step 1 / 6 · vs docker
$ podman ps
no containers yet — start with `podman pull` + `podman run`

Daemonless, rootless — what makes podman different

Docker runs a single privileged daemon (dockerd) that owns every container. Podman doesn't: each `podman run` is a normal process owned by your user, supervised by conmon. Containers run rootless by default — your UID inside the container maps to your UID outside, no root needed. Same CLI verbs as docker (`alias docker=podman` usually just works), but no daemon to crash, no root to compromise.

$podman version
$alias docker=podman
$podman info
// key insight

Three things separate Podman from Docker on RHEL: no daemon, rootless by default, and first-class systemd integration via Quadlet. The first two improve security; the third is what makes containers feel native — they show up in `systemctl status`, log to the journal, and survive reboots like any other service.

// exam-ready · podman + quadlet
$podman pull IMG
$podman run -d --name N -p H:C IMG
$podman run --rm -it IMG sh
$podman ps / ps -a
$podman images
$podman exec -it N bash
$podman logs -f N
$podman inspect N | jq .
$podman stop / start / restart / rm N
$podman rmi IMG
$-v /host:/container:Z
$podman volume create / ls / rm
$~/.config/containers/systemd/X.container
$systemctl --user daemon-reload
$systemctl --user enable --now X.service
$loginctl enable-linger USER
// check yourself
4 quick questions
Q1

Biggest architectural difference between Podman and Docker?

Q2

You bind-mount /srv/html into a container on RHEL with SELinux enforcing. The container can't read the files. What's the fix?

Q3

You want a rootless container to survive reboots. Best modern approach on RHEL 9?

Q4

A rootless `podman run -p 80:80 nginx` fails with a permission error. Why, and the cleanest workaround?

These aren't graded — they're just for active recall, which is what actually makes the lesson stick.

🌳
// where Quadlet plugs in

systemd targets & units

Quadlet turns containers into systemd .service units. Solidify how units + dependencies + targets work and Quadlet stops feeling magical.

open →
// more in linux

keep going — these pair well with what you just learned.

see all linux →
🛡️

SELinux contexts

Why Apache can't read your file. Watch the policy engine decide — and learn the workflow for fixing denials. RHCSA-ready.

8 min · interactiveopen →
⚡

Linux boot process

From power button to login prompt. Every stage in the chain — UEFI, GRUB, kernel, initramfs, systemd — with the rescue moves that save you. RHCSA-ready.

9 min · interactiveopen →
💾

LVM stacking

Layer-by-layer build of an LVM stack: disks → PVs → VG → LVs → filesystem. Then extend live and snapshot. RHCSA-ready.

8 min · interactiveopen →
back to RHCSA trackall lessons