Q: A containerized microservice makes HTTP calls to `api.example.com`. It works perfectly when tested locally on a developer laptop, but fails with DNS resolution errors when deployed inside a Docker container on the CI server. The CI server itself can resolve the domain fine. What is wrong?
Docker containers on user-defined networks use Docker's embedded DNS server (127.0.0.11). On the default bridge network, containers inherit the host's /etc/resolv.conf.
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 DNS resolution, Docker's embedded DNS server.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
Docker containers on user-defined networks use Docker's embedded DNS server (127.0.0.11). On the default bridge network, containers inherit the host's /etc/resolv.conf. However, if the host uses 127.0.0.53 (systemd-resolved's stub resolver), Docker copies this into the container where it's meaningless because the container cannot reach the host's loopback address.
- Per container:
docker run --dns 8.8.8.8 myapp - Globally in
/etc/docker/daemon.json:{"dns": ["8.8.8.8", "8.8.4.4"]} - Or switch the CI server's systemd-resolved to expose on a real interface rather than the loopback stub.
Remediation & Permanent Safeguards
*Fix:* Explicitly configure DNS for the container or Docker daemon:
- Per container: docker run --dns 8.8.8.8 myapp
- Globally in /etc/docker/daemon.json: {"dns": ["8.8.8.8", "8.8.4.4"]}
- Or switch the CI server's systemd-resolved to expose on a real interface rather than the loopback...
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 containerized microservice makes
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 containerized microservice makes
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 containerized microservice makes 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 containerized microservice makes Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.