Image Manifest and Metadata
What you'll learn: How container images describe their internal structure through manifests and metadata in the OCI (Open Container Initiative) format.
The Index Card for a Container
Every container image needs a "recipe card" that explains what's inside. This is the image manifest—a JSON document that serves as the blueprint describing all the layers, configuration, and metadata that make up your image.
Think of it like a detailed package label: it doesn't contain the food itself, but it lists every ingredient, nutritional information, and preparation instructions.
What's Inside a Manifest
The manifest tells the container runtime:
- Layer digests: The cryptographic hashes (SHA-256) identifying each layer in order
- Configuration blob: A reference to the JSON file containing runtime settings (environment variables, exposed ports, default command)
- Media types: The format of each component (e.g.,
application/vnd.oci.image.layer.v1.tar+gzip) - Platform information: Target architecture (amd64, arm64) and operating system
- Size information: How large each layer is
OCI Standard Format
The OCI specification ensures manifests work consistently across Docker, containerd, Podman, and other runtimes. When you pull an image, the runtime first fetches the manifest to understand which layers to download and how to assemble them.
Metadata Layers
Beyond the manifest, images carry additional metadata:
- Image configuration: Default environment, working directory, user
- Labels: Key-value pairs for versioning, authorship, or custom tags
- History: How each layer was created (which command generated it)
Key Takeaway: The image manifest is the structured descriptor that tells container runtimes exactly which layers to retrieve, in what order, and how to configure the resulting container—all in a standardized OCI format.