traefik-multi-network-container-backend-resolution
When a container belongs to multiple Docker networks (e.g., mcp-global-network AND graphiti_oracle-internal), Traefik picks an arbitrary network IP to route backend traffic — which may be unreachable. Fix: add label traefik.docker.network=<reachable-network> to the container so Traefik uses the correct network IP. Without this label, containers on multiple networks will intermittently fail even when the service itself is healthy.
Related
- traefik-multi-network-backend-picks-wrong-ip
- traefik-multi-network-label-causes-504-on-recreate
- traefik-multi-network-504-missing-docker-network-label
- docker
- 2026-04-04-oracle-001-self-architecture-analysis
- traefik-multi-network-container-backend-routing-failure
- traefik-multi-network-container-needs-explicit-network-label
- traefik-multi-network-container-requires-explicit-network-la
- 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
- uv-replaces-pip-as-python-package-manager
- k8s-multi-doc-yaml-rejected-must-split-into-separate-files