DOSSIER 24 / 9 ARTICLES
Docker: from running containers to application orchestration
Follow images, builds, Compose, networking, storage, and production operations through to Swarm and engine selection.
Start with the first articleFollow the question further.
Start with the client-server model and OCI execution chain, then learn image, container, and persistence parameters. Organize applications with Dockerfiles and Compose. Networking, storage, security, and NixOS modules clarify runtime boundaries; Swarm explains multi-node services; a final Podman comparison addresses compatibility and permissions.
- 01
Identify CLI and daemon permissions first; a regular user invoking Docker does not make it rootless.
Docker basics: images, containers, and the daemon
Understand container startup through the client, API, containerd, and OCI runtime.
Read article - 02
Read commands by object lifecycle, checking writable layers, volumes, and images before deletion.
The Docker command line: images, containers, volumes, and networks
Learn common flags and distinguish the effects of running, stopping, and deleting resources.
Read article - 03
Check caches and outputs through the relationships between context, entry points, and build stages; never put credentials in layers.
Dockerfiles and image builds
Organize image recipes around entry commands, multi-stage builds, and cache optimization.
Read article - 04
Distinguish interpolation, injection, readiness, and ongoing health, and check the Compose version and profile behavior.
Compose: defining multi-service applications
Manage single-host applications with services, dependencies, profiles, watch, and secrets.
Read article - 05
Clarify exposed ports, network modes, volume locations, and actual backup consistency.
Docker networking and storage
Choose network modes and persistence methods, with clear port-exposure and data-lifecycle boundaries.
Read article - 06
Turn limits, logs, health, updates, and data recovery into practical acceptance checks.
Docker in production: resources, security, and recovery
Check container operating conditions through limits, logs, updates, credentials, and backups.
Read article - 07
Check daemon.settings, credential files, and coexistence options in the pinned Nix modules.
Declaring Docker and containers on NixOS
Organize engine settings, container definitions, and credential inputs with system modules.
Read article - 08
Review the legacy v3 format and multi-node storage before assessing what cluster scheduling can recover.
Swarm: from service replicas to cluster orchestration
Understand stacks, overlay networks, and rolling updates, and check Compose compatibility boundaries.
Read article - 09
Compare permissions, APIs, builds, and orchestration individually. Docker and Podman can coexist, but they are not complete replacements for each other.
Docker and Podman: architecture, compatibility, and coexistence
Compare engine control models, permissions, and ecosystems to choose tools by workload.
Read article