Page 2 - Docker

AI generated

Supply Chain Security for Docker Base Images

Maxim Mironjuk - April 18, 2026

Every Docker image starts with a base image that the whole team trusts blindly, usually referenced by a tag like latest or a version number without further checks. Supply chain security replaces that blind trust with pinned digests, cryptographic signatures, and traceable provenance information, so a compromised base image does not silently reach production deployments.

Docker PHP

AI generated

Bringing Node, PHP, and Composer Together in Docker Containers

Maxim Mironjuk - April 17, 2026

PHP projects need Composer for backend dependencies and Node for asset compilation. Forcing both into a single container is the wrong move, and running both on the host is impractical. Multi-stage builds and cleanly separated build containers solve this elegantly.

Docker Git

AI generated

Running Parallel Feature Environments with Compose Project Names and Profiles

Maxim Mironjuk - April 14, 2026

Anyone needing to check multiple feature branches at the same time quickly hits the limits of a single Docker Compose stack: port conflicts, shared databases and naming collisions between containers and networks. COMPOSE_PROJECT_NAME combined with profiles solves exactly this problem by letting every environment run side by side, cleanly isolated.

Docker Security/OWASP

AI generated

Production Docker Checklist: Security, Performance, Storage, and Deployments

Maxim Mironjuk - April 08, 2026

Containers on a developer laptop and containers in production are two fundamentally different things. This Docker checklist covers every mandatory category: security hardening, performance limits, storage protection, and repeatable deployment procedures, with concrete commands for each item.

Docker Security/OWASP Testing/E2E

AI generated

Docker Image Scanning and Security Updates in CI

Maxim Mironjuk - April 07, 2026

A Docker image that gets built once and never checked for vulnerabilities again slowly turns into a security hole. Image scanning in the CI pipeline and automatic base image updates close that window before CVEs make it into production.

Docker

AI generated

Alternative Container Registries Beyond Docker Hub

Maxim Mironjuk - March 25, 2026

Docker Hub was the default answer for years to the question of where images get stored, yet rate limits, cost and compliance requirements are increasingly pushing teams toward alternative container registries. GitLab, GitHub, Amazon ECR and self hosted Harbor offer different answers to the same question, which registry fits which situation.

Docker

AI generated

Build Once, Deploy Many: Moving One Docker Image Through Every Stage

Maxim Mironjuk - March 20, 2026

Anyone who builds a separate Docker image for every environment loses the exact guarantee containers are supposed to provide. Build once, deploy many separates the build step from configuration and ensures that the artifact running in production is exactly the one that was tested in staging, without a single rebuild in between.

Docker

AI generated

Rolling Updates in Docker Swarm Without Downtime

Maxim Mironjuk - March 17, 2026

A rolling update replaces containers step by step with new versions, while the service stays continuously reachable for users. Without correctly configured health checks, parallelism and rollback rules, though, a single faulty deployment can still lead to a noticeable outage that a well designed rolling update prevents from the start.

Docker Security/OWASP

AI generated

Runtime Threat Detection in Containers with Falco

Maxim Mironjuk - March 14, 2026

Image scanning finds known vulnerabilities before startup, but once a container is running, much stays invisible. Falco watches system calls directly in the kernel and detects in real time when a process inside a container behaves differently than expected, for example an unexpected shell, a write to sensitive paths, or an escape attempt.

Docker

AI generated

One Process per Container: When the Rule Helps and When It Doesn't

Maxim Mironjuk - March 07, 2026

"One process per container" is one of the most frequently quoted Docker principles, and one of the most frequently misapplied. What the principle really means, where it makes sense, and when Supervisor, s6-overlay or dumb-init are the better decision.