KevsRobots Learning Platform
49% Percent Complete
By Kevin McAleer, 2 Minutes
Page last updated May 24, 2025

Now that you know what makes Podman powerful, let’s get hands-on with managing containers and images.
You’ll use the Podman CLI to list, inspect, stop, remove, and troubleshoot containers — just like you would with Docker, but daemonless and rootless.
podman ps
podman ps -a
podman inspect <container-id>
🧠 This returns detailed JSON output including network, storage, environment variables, and more.
podman start <container-id>
podman stop <container-id>
podman rm <container-id>
🛑 Always stop a container before removing it, unless you use
-f(force).
podman pull ubuntu
podman images
podman rmi <image-id>
🔍 Need more control? Use
podman image inspectorpodman image historyto see build layers and metadata.
podman volume create mydata
podman run -v mydata:/data alpine
podman volume ls
podman volume rm mydata
📁 Podman volumes live under
~/.local/share/containers/storage/volumes(in rootless mode).
podman logs <container-id>
podman logs -f <container-id>
📜 Podman log output goes to the standard user log files in rootless mode. Combine with
journalctlfor systemd-managed containers.
podman cp myfile.txt <container-id>:/root/
podman exec -it <container-id> bash
podman container prune
podman image prune
Next up: Working with Pods
You can use the arrows ← → on your keyboard to navigate between lessons.
Comments