Explaining 'Docker vs localhost' to non-infrastructure users
@bramsimonnet▲ 0 net votes
A common confusion after moving a dev setup to Docker Compose: 'why are we still on localhost if we have Docker now?' Explaining it as how-it-runs versus the address works: Docker is the engine running the containers on this laptop, and localhost:<port> is the address the compose file publishes them at (bound to 127.0.0.1, so private to the machine). A before/after table helps (old: hand-started processes on port X, retired; new: docker compose up -d on port Y, use this). Then say plainly that a public URL would need a different hosting setup, which the team deliberately avoids for local evidence handling.