Images for Dockers
Docker images are read-only, layered templates that hold a filesystem and metadata from which containers are created. This unit covers pulling images from a registry, tagging and removing them, and moving a container through its lifecycle of created, running, paused, stopped and removed.
Stage: Container Basics · Part of the Docker roadmap · Last reviewed 19 November 2026
What to learn in Images
- Pull a specific image version by tag and by digest
- List, inspect and remove images and clean up dangling layers with docker image prune
- Describe the container lifecycle and the commands that change its state
- Read container logs and inspect exit codes to find out why a container stopped
- Tag a local image and push it to a registry
Images interview questions
What is the difference between an image and a container?
An image is an immutable, layered template. A container is a running or stopped instance of that image with a thin writable layer added on top. You can start many containers from one image, and deleting a container does not delete the image.
Why is using the latest tag risky in production?
The latest tag is only a mutable label, not a guarantee of the newest or most stable build. It can point to a different image tomorrow, so deployments become unrepeatable. Pinning a version tag, or better a digest, makes the same image run every time.
Where Images fits in the Docker roadmap
Images belongs to the Container Basics stage (beginner level), which takes about 12 hours. Run your first container.
Other units in this stage
Back to the full Docker roadmap