AON Diagram of Docker Container Layers Infographic

Tech architecture infographic titled "Docker Container Layers" using PROTOCOL HANDSHAKE (numbered exchanges) archetype. Show a clean, executive-friendly explanation of how Docker container layers work as a sequence of numbered exchanges between clearly labeled boxes connected by directional arrows. Use labeled boxes for: Developer Workstation, Docker CLI, Docker Engine, Base Image Layer, Read-Only Image Layers, Writable Container Layer, Container Runtime, Local Image Cache, Container Registry, Build Context Filesystem, and Running Container. Also include supporting boxes named Browser, API, DB, Cache, Queue as generic reference components in a small side rail, each with icon, canonical English name, and one-line role description, connected with simple arrows to indicate typical application dependencies without implying they are required for every container. Every box must contain: a simple icon, a component name in English, and a one-line role description in English.

Depict the main numbered exchange flow accurately: 1) Developer Workstation sends build or run command to Docker CLI. 2) Docker CLI sends Docker API request to Docker Engine over local Unix socket or named pipe. 3) Docker Engine checks Local Image Cache for requested image layers. 4) If layers are missing, Docker Engine requests image manifest and layer blobs from Container Registry over HTTPS. 5) Container Registry returns manifest JSON and compressed layer tarballs. 6) Docker Engine assembles stacked read-only image layers using union filesystem semantics. 7) Docker Engine creates a new Writable Container Layer above the read-only stack and starts the Container Runtime. 8) Running Container reads files from lower image layers and writes changes only to the writable top layer. 9) Optional side arrows show app traffic from Running Container to API, DB, Cache, and Queue using canonical labels like REST JSON, SQL query, cache GET/SET, and async message.

Arrow labels must be short and in English, for example: "docker build", "Docker API request", "cache lookup", "HTTPS manifest request", "manifest JSON", "layer blob", "read-only layer", "copy-on-write", "container start", "REST JSON", "SQL query", "cache GET/SET", "async message". Make the flow technically accurate: Docker layers are immutable read-only image layers plus one writable container layer; registry transfer uses HTTPS; image manifest is JSON metadata; layer filesystem behavior is copy-on-write / union filesystem style. Do not imply audited security guarantees.

Add a numbered legend 1-7 in English summarizing lifecycle for non-technical exec readers: 1. Command starts a build or run action. 2. Engine receives the request through Docker API. 3. Local cache avoids re-downloading existing layers. 4. Missing layers are pulled from registry over HTTPS. 5. Image layers are stacked as read-only filesystem layers. 6. A writable top layer is added for container-specific changes. 7. The container runs while preserving the original image layers unchanged.

Visual style: minimal flat, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use a developer pink & teal palette with soft neutrals, subtle depth, rounded rectangles, crisp arrows, sparse executive-friendly composition, modern clean typography, calm confident mood, high contrast labels, lots of whitespace, and simple generic cloud icons for the registry/network area. Include small callouts such as "Immutable image layers" and "Writable top layer". No real cloud-vendor logos, no AWS, GCP, or Azure branding, no watermarks.

All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real cloud-vendor logos (AWS, GCP, Azure) beyond generic cloud icons. Common protocol names (HTTPS, TCP, JWT, OAuth, REST, GraphQL) stay in canonical English form. No security-claim overstatements (do not present diagrams as audited reference architectures).