Docker: Guides and Practical Know-how | Page 3 | mironsoft Blog
Docker
-
Apr 7, 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.
-
Mar 31, 2026
helm upgrade --install is quick to type, but without lint, diff and rollout verification it stays unclear whether a deployment was actually successful. Bash automation around Helm deployments checks charts before applying them, actively waits for a healthy rollout, and automatically rolls back to the last working revision on failure.
-
Mar 29, 2026
only and except were the standard way to run jobs conditionally in GitLab CI for years, but the rules keyword has superseded both for a long time and enables condition logic that only/except simply cannot express. This article shows why the migration pays off and how it succeeds step by step in existing pipelines.
-
Mar 26, 2026
Four different sources for environment variables, one precedence order that is rarely documented well: when a value never reaches a container, or a different one shows up than expected, an unclear precedence between shell environment, the .env file, the environment block, and env_file is almost always the cause.
-
Mar 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.
-
Mar 24, 2026
A poorly ordered Dockerfile can rebuild every single layer on every build, even when only one line of application code changed. Understanding how Docker invalidates its layer cache based on Dockerfile order lets teams cut CI build times dramatically, without spending a cent more on hardware.
-
Mar 21, 2026
Anyone building Magento modules without integration tests only notices regressions in staging or in production. The Magento Test Framework provides a complete environment with real database isolation, automatic fixture management and the full Magento DI container, provided it is set up correctly.
-
Mar 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.
-
Mar 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.
-
Mar 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.