Load Balancer AWS Diagram in Docker Container Layers

Tech architecture infographic titled "Docker Container Layers" using archetype HOW-IT-WORKS. Show a clean layered system diagram explaining how Docker images and containers are built and run. Center the composition around a vertical stack of labeled BOXES with ARROWS showing dependency and runtime flow. Include these components: Source Code box with code-file icon, label "Application Source", role "App files and dependency manifests"; Dockerfile box with document icon, label "Dockerfile", role "Build instructions for image layers"; Base Image box with OS cube icon, label "Base Image", role "Starting filesystem and runtime"; Layer 1 box, label "OS Packages Layer", role "Installed system packages and tools"; Layer 2 box, label "Dependencies Layer", role "Language libraries and package dependencies"; Layer 3 box, label "Application Layer", role "Copied application code and assets"; Layer 4 box, label "Config / Metadata Layer", role "Entrypoint, env, ports, labels"; Image Manifest box with registry-tag icon, label "Image Manifest", role "References ordered read-only layers"; Container Runtime box with engine icon, label "Docker Engine", role "Creates runnable container from image"; Writable Layer box with pencil-disk icon, label "Container Writable Layer", role "Temporary runtime file changes"; Running Process box with terminal icon, label "PID 1 Process", role "Main application process inside container"; Volume box with disk icon, label "Mounted Volume", role "Persistent data outside image layers"; Registry box with generic cloud icon, label "Container Registry", role "Stores and distributes image artifacts". Connect with technically accurate ARROWS and short labels: Source Code to Dockerfile "build context"; Dockerfile to Base Image "FROM"; Dockerfile to OS Packages Layer "RUN apk/apt install"; Dockerfile to Dependencies Layer "RUN npm/pip install"; Dockerfile to Application Layer "COPY source files"; Dockerfile to Config / Metadata Layer "CMD / ENTRYPOINT / ENV / EXPOSE"; all read-only layers to Image Manifest "ordered layer digests"; Image Manifest to Registry "push image"; Registry to Docker Engine "pull image"; Image Manifest to Docker Engine "image reference"; Docker Engine to Container Writable Layer "create writable top layer"; read-only layers plus writable layer to Running Process "union filesystem mount"; Running Process to Mounted Volume "read/write persistent data". Add small side annotation boxes for concepts: "Read-Only Layers" with role "Cached and shared across images"; "Union Filesystem" with role "Merges layers into one view"; "Layer Cache" with role "Reuses unchanged build steps". Add a numbered legend 1-7 in English: 1. "Docker reads the Dockerfile and build context." 2. "Each instruction creates or reuses a cached read-only layer." 3. "The final image is recorded as a manifest that orders the layers." 4. "The image can be pushed to or pulled from a container registry." 5. "Docker Engine creates a container by stacking image layers." 6. "A writable top layer is added for runtime file changes." 7. "The main process runs, optionally using mounted volumes for persistent data." Visual style: retro 1980s computing, blueprint cyan palette, glowing cyan lines on deep navy background, grid paper blueprint texture, subtle CRT monitor feel, neon wireframe accents, precise technical drafting mood, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Audience: mid-level developer, so keep labels practical and technically accurate, not marketing-like, and do not imply audited security guarantees. 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).