Q: You set up a strict UFW (Uncomplicated Firewall) on your Ubuntu server to block all incoming traffic to port 8080. You then run a Docker container `docker run -p 8080:80 myapp`. Miraculously, a hacker easily accesses your app on port 8080 from the internet. Why did the firewall fail?
Docker bypasses UFW by design.
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: "In an interview, I explain how we diagnosed container runtime failures without guessing. The interviewer is testing: Docker networking vs. Host iptables/UFW integration.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
Docker bypasses UFW by design. When Docker starts, it actively manipulates the Linux iptables directly by inserting its own rules at the absolute top of the PREROUTING chain in the nat table (in a chain called DOCKER). Because UFW operates primarily in the INPUT chain, the traffic hitting port 8080 is intercepted by Docker's PREROUTING rule *before* UFW ever sees it, and routed directly into the container. *Fix:* Never rely on host OS firewalls to protect exposed Docker ports. You must either not publish the port 8080 to the internet (bind it to localhost -p 127.0.0.1:8080:80), or modify the Docker daemon configuration to set "iptables": false (which breaks many standard Docker networking features).
- Immediate Triage: Docker bypasses UFW by design.
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
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 strict (Uncomplicated Firewall)
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 strict (Uncomplicated Firewall)
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 strict (Uncomplicated Firewall) 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 strict (Uncomplicated Firewall) Bridge networking utilizes iptables NAT translations which add latency overhead, whereas host networking bypasses the network namespace entirely.