Page 7 - Docker

Docker

AI generated

Structuring Docker Compose Cleanly: Services, Profiles, Overrides, and .env Files

Maxim Mironjuk - July 15, 2025

Anyone who crams every environment into a single docker-compose.yml will soon be fighting configuration drift, hardcoded passwords, and deployments that behave differently locally than in CI. Profiles, overrides, and cleanly separated .env files solve exactly these problems, without the Compose project growing into something unreadable.

Docker

AI generated

Macvlan Networks: Use Cases and Limitations

Maxim Mironjuk - July 11, 2025

A macvlan network gives containers their own IP address visible on the physical network, with no port mapping through the Docker host at all. This solves real problems for legacy applications and monitoring systems, but comes with a known limitation around communication between host and container that must be understood before going to production.

Docker

AI generated

Choosing the Right Docker Log Driver: json-file vs. journald

Maxim Mironjuk - July 11, 2025

Docker's default setting is rarely the right choice for production environments. The log driver json-file only rotates logs after explicit configuration and exists as a plain text file, while journald integrates logs directly into the systemd journal infrastructure, with structured metadata and central querying via journalctl.

Docker Testing/E2E

AI generated

Linting and Testing Dockerfiles and Compose Files: hadolint, trivy, docker compose validate

Maxim Mironjuk - July 09, 2025

Dockerfiles that are never statically checked accumulate silent problems: outdated base images with critical CVEs, invalid compose configurations, and structural issues that only surface once they hit production. Automated linting and testing closes that gap right inside the CI pipeline.

Docker Design Patterns

AI generated

Docker Swarm vs Kubernetes: When Each Orchestration Fits

Maxim Mironjuk - July 08, 2025

Docker Swarm and Kubernetes solve the same core problem, running containers reliably across multiple hosts, but with completely different operational effort. Teams that base the decision purely on how popular Kubernetes is often build in unnecessary complexity that nobody actually needs day to day.

Docker

AI generated

Overlay Networks Across Multiple Docker Hosts

Maxim Mironjuk - June 25, 2025

A bridge network ends at the boundary of a Docker host. As soon as a setup spans multiple physical or virtual machines, an overlay network takes over communication between containers, no matter which host they actually run on, encrypted and with built-in load balancing.

Docker

AI generated

Running Cronjobs and Workers in Docker the Right Way

Maxim Mironjuk - June 24, 2025

Anyone who drops cronjobs and worker processes into an existing Docker container without a plan will sooner or later run into PID 1 zombies, lost signals and uncontrolled restarts. Dedicated containers, supervisor and clean signal handling replace fragile setups with predictable, production ready background processes.

Docker

AI generated

Multi-Arch Images with Docker Buildx

Maxim Mironjuk - June 23, 2025

Multi-arch images solve the problem of a team developing on Apple Silicon laptops but deploying to amd64 servers, or the reverse case of using arm64 instances in production. Docker Buildx produces images for multiple architectures from a single build command and publishes them under one shared tag as a manifest list.

Docker Testing/E2E

AI generated

Building a Container Based Test Matrix for Multiple Runtime Versions

Maxim Mironjuk - June 13, 2025

A test matrix with Docker checks an application against several PHP or Node versions at the same time, instead of relying on a single local developer version. Containers make every combination reproducible, executable in parallel, and clearly separable in the results, without maintaining multiple physical test machines.

Docker

AI generated

Designing Docker Compose for Local Development Environments the Right Way

Maxim Mironjuk - June 02, 2025

A local development environment built with Docker Compose is more than a running container. Get bind mounts wrong and you lose performance. Hardcode secrets in the compose file and you put the whole project at risk. Skip an onboarding concept and you lose hours with every new team member. This guide shows how to get it right from day one.