traefik-multi-network-container-requires-explicit-network-label
When a Docker container is attached to multiple networks (e.g., mcp-global-network + graphiti_oracle-internal), Traefik arbitrarily picks a network to resolve the backend IP — often the wrong one it cannot reach. Root cause: no traefik.docker.network label to disambiguate. Fix: add traefik.docker.network=<reachable-network> label to the container’s compose definition and recreate. Symptom is timeout on MCP initialize, not a clear 502.
Related
- traefik-multi-network-container-backend-routing-failure
- traefik-multi-network-backend-picks-wrong-ip
- traefik-multi-network-container-needs-explicit-network-label
- traefik-multi-network-container-backend-resolution
- traefik
- traefik-multi-network-backend-resolution-failure
- traefik-multi-network-missing-label-routes-wrong-ip
- traefik-multi-network-missing-label-picks-wrong-backend-ip
- traefik-multi-network-container-missing-label-gotcha