Docker Container Layers Network Schema Infographic

Tech architecture infographic titled "Docker Container Layers" using archetype HOW-IT-WORKS. Show a clean numbered technical diagram explaining how Docker image and container layers work for a mid-level developer. Use labeled BOXES connected by ARROWS showing data and dependency direction. Include these components as stacked and side-side boxes: Source Code (icon: code file, role: "Application source and build context"), Dockerfile (icon: document, role: "Build instructions for image layers"), Base Image Layer (icon: package stack, role: "Starting filesystem from parent image"), Dependency Layer (icon: cubes, role: "Installed OS packages and libraries"), Application Layer (icon: app window, role: "Copied app code and runtime assets"), Configuration Layer (icon: sliders, role: "Environment defaults and metadata"), Image Manifest (icon: list, role: "References ordered read-only layers"), Container Runtime (icon: engine, role: "Creates and runs containers from image"), Writable Container Layer (icon: pencil on disk, role: "Stores runtime file changes"), Volume Storage (icon: database cylinder, role: "Persists data outside container layer"), Union Filesystem (icon: stacked layers, role: "Merges layers into one mounted view"), Registry (icon: generic cloud, role: "Stores and distributes image layers"), Host Kernel (icon: chip, role: "Provides shared OS kernel to containers"). Also include generic supporting labeled boxes to satisfy network schema expectations: Developer CLI (icon: terminal, role: "Builds, tags and runs images"), Local Cache (icon: cache, role: "Reuses unchanged build layers"), Network Bridge (icon: network nodes, role: "Connects containers to network interfaces"). Use arrows with short English labels such as: "docker build context", "build instruction", "creates layer", "cache hit", "push layer blob", "pull manifest", "mount merged view", "runtime write", "bind volume I/O", "syscall to kernel", "container network traffic". Compose the main visual as a vertical stack of read-only image layers, then a top writable container layer, with side arrows to registry, cache, volumes, kernel, and network bridge. Add small callouts noting: "Read-only layer", "Copy-on-write", "Layer cache reuse", "Shared base layers", "Container = image + writable layer". Add a numbered legend (1-7) in English walking through lifecycle: 1. Developer runs docker build using source code and Dockerfile. 2. Each Dockerfile instruction creates or reuses a cached read-only layer. 3. Docker stores ordered layers and manifest as an image. 4. Image layers can be pushed to or pulled from a registry as content-addressed blobs. 5. docker run creates a container by mounting image layers through a union filesystem. 6. A thin writable container layer captures file changes while persistent data can go to volumes. 7. The running container uses the host kernel and network bridge for process execution and connectivity. Visual style: dark-mode developer, dark mode neon palette, glowing cyan, purple, magenta, and electric green accents on charcoal background, high contrast, modern editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Mood: precise, technical, polished, educational, not a security-certified reference architecture. 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).