Podman Fundamentals
The daemonless, rootless container engine explained from first principles. Learn how Podman differs from Docker — and remember it with spaced repetition.
- flashcards
- 75
- flashcards
- per day
- ~10 min
- per day
- level
- Beginner → Intermediate
- level
- modules
- 5
- modules
What is Podman?
Podman is an open-source container engine for building, running and managing OCI containers and images. Its defining trait is that it is daemonless: instead of a central background service, each container runs as a direct child of the podman command. That removes the single-point-of-failure daemon and lets containers run rootless — as an unprivileged user rather than root.
Because its CLI mirrors Docker’s, most Docker commands work unchanged (often via alias docker=podman). But Podman adds concepts Docker lacks: pods that group containers around shared namespaces like a Kubernetes Pod, image builds handed to Buildah, registry transfers handled by Skopeo, and deployment through systemd using Quadlet unit files.
It has become the default container tool on Fedora and RHEL and a common drop-in Docker replacement for security-conscious teams — which makes it a natural next step after the Docker fundamentals.
5 modules, seed to bloom
Each module is a set of flashcards — 75 in total. Answer, review, and watch your knowledge grow from seed to full bloom.
Core Concepts
Daemonless architecture, Docker CLI compatibility, OCI, and the rootful vs rootless model
15 cardsRootless Containers
User namespaces, subuid/subgid mapping, rootless networking, and port caveats
15 cardsPods & Multi-Container
Podman pods, shared namespaces, the infra container, and Kubernetes-style YAML
15 cardsImages & Registries
Building with Buildah, moving images with Skopeo, registries.conf, and short-names
15 cardssystemd & Deployment
Quadlet units, auto-start with systemd, lingering, and Compose vs Kubernetes YAML
15 cardsSample questions
A taste of the real flashcards. Pick an answer, then reveal the explanation.
What is Podman's defining architectural difference from Docker?
- AIt is daemonless — each container runs as a child process of the podman command
- BIt is VM-based — each container runs inside its own lightweight hypervisor guest
- CIt is agent-based — a per-node agent pulls container specs from a control plane
- DIt is client-server — a persistent root daemon brokers every container request
Which kernel feature lets rootless Podman map container root to an unprivileged user?
- AUser namespaces — they remap container UIDs onto the host's unprivileged range
- BControl groups — they cap the CPU and memory a container is allowed to consume
- CSeccomp filters — they restrict which system calls a container may invoke
- DCapabilities — they split root's powers into individually grantable privileges
What is a Podman pod?
- AA group of containers that share selected namespaces, like a Kubernetes pod
- BA single container image bundled together with all of its build layers
- CA remote registry namespace that groups related images under one account
- DA snapshot of a running container saved for later restart or rollback
What is Quadlet?
- AA systemd generator that runs Podman containers from declarative unit files
- BA standalone daemon that supervises Podman containers outside of systemd
- CA GUI dashboard for monitoring the health of running Podman containers
- DA CLI plugin that converts Compose files into Docker Swarm stack definitions
Learn it once, keep it for good
Answer a question
Each card is one practical concept with multiple options. Pick what you think is right.
Get the full answer
See the correct option plus a clear explanation, and a link to deeper docs when one is available.
Review at the right time
A spaced-repetition engine (SM-2 or FSRS) resurfaces each card just before you would forget it.
Why Podman is worth your time
Rootless by default
Running containers as an unprivileged user shrinks the blast radius of an escape — a major security win over a root-owned daemon.
Docker-compatible
The CLI matches Docker’s, so your existing muscle memory and command lines carry over with little more than an alias.
Kubernetes-friendly
Podman pods mirror Kubernetes Pods, and it can generate and play Kubernetes YAML — a gentle bridge from a laptop to a cluster.
systemd-native
Quadlet turns containers into first-class systemd services with auto-restart, ordering and boot-time start — no extra supervisor.
Common questions
Do I need to know Docker first? +
It helps but is not required. Podman shares Docker’s CLI and concepts, so this track calls out the differences — daemonless, rootless, pods — and works whether you are coming from Docker or starting fresh.
How long does it take? +
About 10 minutes a day. Spaced repetition means short, frequent sessions beat cramming — most learners get comfortable with the fundamentals within a couple of weeks.
Is it free? +
Yes, completely free. No registration or credit card is required, and all your progress is stored locally in your browser.
Is Podman a drop-in replacement for Docker? +
For most everyday commands, yes — the CLI is Docker-compatible. The differences worth learning are the daemonless, rootless model, pods, and building and deploying with Buildah, Skopeo and systemd Quadlet, all of which this track covers.
Ready to learn Podman?
Plant your first seed today. Ten minutes a day is all it takes to grow real, lasting container skills.