Q: You need to verify whether a Docker image tagged `myapp:v2.1.0` in your registry is truly a multi-architecture image that supports both `linux/amd64` and `linux/arm64`, without pulling the entire image. How do you inspect this remotely?
Use docker manifest inspect to query the registry's manifest list without downloading any image layers:
docker manifest inspect.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third.""
Want to master this scenario in a live sandbox? KodeKloud's Docker Certified Associate (DCA) Hands-On Lab Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When containerizing our microservices stack, container lifecycle and resource management were critical. The interviewer is testing: OCI image manifests, manifest lists, docker manifest inspect.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Use docker manifest inspect to query the registry's manifest list without downloading any image layers: For a multi-arch image, this returns a manifest list (also called a "fat manifest") containing multiple entries — one per platform. Each entry specifies the architecture, os, and a digest pointing to the platform-specific image manifest. If the image is single-architecture, the command returns a single image manifest with layer digests instead of a list. You can also use tools like crane (from Google's go-containerregistry): Or skopeo: skopeo inspect --raw docker://myregistry.com/myapp:v2.1.0 | jq . These tools query the registry API directly, never downloading image layers.
docker manifest inspect myregistry.com/myapp:v2.1.0
- Immediate Triage: Use docker manifest inspect to query the registry's manifest list without downloading any image
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Structuring Dockerfile instructions inefficiently by copying app source before package manifests when configuring need verify whether
Copying code before package manifests (
package.json,go.mod,requirements.txt) invalidates the build cache on every commit, forcing slow full reinstalls. -
Neglecting the PID 1 process reap problem and omitting proper SIGTERM signal forwarding when configuring need verify whether
If an application runs as PID 1 without an init system (like
tini), it fails to reap zombie child processes and ignoresSIGTERMsignals, causing unclean 10s timeouts. - Assembling single-stage images containing compilers, build SDKs, and header files in production when configuring need verify whether Single-stage builds bloat image size by gigabytes and expose extensive package vulnerabilities; multi-stage builds isolate artifacts into minimal distroless images.
- Confusing container port forwarding on bridge networks with unisolated host networking mode when configuring need verify whether Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.