This article explains how Docker images are built on UnionFS with overlay2, describes the rootfs and layer design, details how containers mount image layers, outlines the directory layout of a Docker registry, and walks through the complete image upload, mounting, and security processes.
This article explains Docker's OverlayFS/Overlay2 storage driver, detailing its layered image architecture, union‑mount mechanics, read/write behavior, metadata organization, and the roles of image, layer, and init layers within the container filesystem.
This article reviews the key features, advantages, and command‑line examples of major Linux file systems—including ext4, Btrfs, XFS, ZFS, F2FS, and OverlayFS—to help you select the most suitable one for performance, reliability, and specific workload requirements.
This article walks you through creating a lightweight Docker‑like container runtime using Bash, explaining Linux namespaces, cgroups, and overlayfs, showing how to inspect and manipulate them, and providing a complete 130‑line script that implements pull, build, run, exec, logs, and cleanup operations.
This tutorial demonstrates how to build a lightweight Docker‑like container runtime using Bash by exploring Linux namespaces, cgroups, and overlayfs, providing step‑by‑step commands, code examples, and a full script that mimics core Docker functionalities for deeper operational understanding.
The article walks readers through building a minimal Docker‑like container runtime entirely in shell, explaining and demoing Linux namespaces, cgroups, and OverlayFS for isolation, resource control, and layered filesystems, and culminates in a concise Bocker script that implements core Docker commands.
This article explains Docker image fundamentals and presents four practical techniques—removing package caches, ordering layers by change frequency, separating build and runtime stages, and inspecting layers with dive—to dramatically shrink image size, speed up builds, and improve security.
This article explains how NFS represents files with file handles, details the generation and decoding mechanisms via export_operations, examines the exportfs API implementation, and explores practical applications such as overlayfs integration and the name_to_handle_at/open_by_handle_at syscalls, providing code examples and kernel‑level insights.
OverlayFS is a stacking file system that merges lower and upper directories into a single view using mount options like lowerdir, upperdir, and workdir, supports copy‑up, whiteouts, opaque directories and configurable rename handling, and is employed in Android, OpenWRT, and container platforms to provide writable overlays on read‑only layers.
This article explores Docker images in depth, covering their fundamental concepts, layered storage mechanisms, the relationship with Dockerfiles and containers, practical optimization techniques for size and build speed, and essential security best practices for creating robust, efficient container images.
This article explains the concept of union file systems, compares implementations such as UnionFS, aufs, OverlayFS, ZFS and Btrfs, and demonstrates how Docker leverages OverlayFS with copy‑on‑write layers to create lightweight, fast‑starting containers.
The article explains how Google and Facebook avoid Docker images by using monolithic repositories and unified build systems, detailing alternative packaging methods like tarballs, XAR, overlay filesystems, and the challenges of achieving efficient layered caching without containers.
The article surveys several unconventional Linux filesystems—OverlayFS for layered read‑only overlays, IncFS enabling incremental app loading, ZoneFS exposing zoned block device zones, LTFS bringing true file‑system semantics to magnetic tape, and StegFS hiding data steganographically—highlighting their unique designs and use cases.
The article explains how Google and Facebook’s monolithic repositories and unified build systems let them avoid Docker images by using direct module transfer, tarballs, XAR files, and overlay filesystems, while highlighting the technical trade‑offs and challenges of layered caching in large‑scale clusters.
This article explains how Linux containers achieve lightweight virtualization through namespaces and cgroups for resource isolation, describes Docker image layering with overlayfs, and walks through container engine internals such as containerd, its shim architecture, and the start/exec workflows.
This article examines Docker image storage technologies, compares overlayfs and device-mapper drivers, and introduces Speedy, an open‑source distributed backend storage system for Docker images, detailing its architecture, modules, and upload/download workflows.
