Docker didn't break my backend. Docker revealed how tightly my app was coupled to my local setup.
Inaph Khadka
2 min read
- Backend API works
- Private routes secured
- Docker build successful
- API unreachable
- localhost betrayed me
- Docker exposing all my bad assumptions
I tried to make my backend API private, and Docker said: "Cool… but who told you localhost exists here?"
- localhost inside Docker ≠ your machine
- ENV variables behave differently when they're actually real
- Network isolation doesn't care about your dev shortcuts
- Security + containers = instant reality check
Docker didn't break my backend. Docker revealed how tightly my app was coupled to my local setup.
- Explicit service networking
- Proper internal-only APIs
- No magic ports
- Zero trust between containers
Painful? Yes. Educational? Absolutely. Will I trust localhost again? Never.
What's the most cursed Docker bug you've faced?
Reactions and discussion
Up next · more on docker
Mar 2026 · 1 min read
Docker vs Kubernetes: simplicity vs orchestration
If Docker is a single railway track, Kubernetes is the entire railway network.