Q: A production container running an API gateway is performing well but you notice its writable layer is growing by 500MB per day. The application itself doesn't write data to disk intentionally. What is causing the growth and how do you stop it?
The application or its runtime is writing files to the container's writable layer (the thin read-write layer on top of the image layers).
Want to master this scenario in a live sandbox? KodeKloud's Docker Certified Associate (DCA) Hands-On Lab Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Container stability relies on clean signal handling (SIGTERM vs SIGKILL) and immutable image tagging. The interviewer is testing: Container writable layer, log files, and read-only filesystem.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
The application or its runtime is writing files to the container's writable layer (the thin read-write layer on top of the image layers). Common culprits: application logs not sent to stdout, temp files, DNS resolver cache, or library-generated cache files.
- Redirect all logs to stdout/stderr instead of files.
- Mount writable paths as volumes or tmpfs so writes bypass the container layer.
- Run the container with a read-only root filesystem:
docker run --read-only --tmpfs /tmp --tmpfs /var/run myapp. This forces you to explicitly declare every writable path, preventing unexpected layer growth.
Remediation & Permanent Safeguards
*Diagnosis:* Run docker diff to see every file added (A), changed (C), or deleted (D) in the writable layer since the container started. *Fix:*
- Redirect all logs to stdout/stderr instead of files.
- Mount writable paths as volumes or tmpfs so writes bypass the container layer.
- Run the container with a read-only root filesystem: docker run --read-only --tmpfs /tmp --tmpfs /...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
-
Structuring Dockerfile instructions inefficiently by copying app source before package manifests when configuring container running gateway
Copying code before package manifests (
package.json,go.mod,requirements.txt) invalidates the build cache on every commit, forcing slow full reinstalls. -
Neglecting the PID 1 process reap problem and omitting proper SIGTERM signal forwarding when configuring container running gateway
If an application runs as PID 1 without an init system (like
tini), it fails to reap zombie child processes and ignoresSIGTERMsignals, causing unclean 10s timeouts. - Assembling single-stage images containing compilers, build SDKs, and header files in production when configuring container running gateway Single-stage builds bloat image size by gigabytes and expose extensive package vulnerabilities; multi-stage builds isolate artifacts into minimal distroless images.
- Confusing container port forwarding on bridge networks with unisolated host networking mode when configuring container running gateway Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.