Q: A containerized app can't connect to a database container on the same Docker host. What's wrong?
By default, containers are isolated. They need to be on the same Docker network. Create a network: docker network create app-net. Run bot...
#Docker #Docker #L2 #Containers #Linux
🎙️ Candidate Opening & Architectural Context
""During an image optimization initiative across our services, we solved this exact problem. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
🛠️ Production Runbook & Step-by-Step Resolution
1️⃣
Production Solution & Architecture
By default, containers are isolated. They need to be on the same Docker network. Create a network: docker network create app-net. Run both containers with --network app-net. Then use the container name as hostname. If using Docker Compose, all services in the same compose file are auto-networked.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: By default, containers are isolated. They need to be on the same Docker network. Create a network: docker network create app-net. ."
⚡ 60-Second Elevator Pitch Talking Points
- Immediate Triage: By default, containers are isolated. They need to be on the same Docker network. Create a netwo
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Advertisement