traefik-multi-network-container-needs-explicit-network-label

When a Docker container is attached to multiple networks, Traefik picks the wrong backend IP unless traefik.docker.network=<network> label is explicitly set. Without this label, Traefik resolves to an unreachable internal network IP (e.g., 172.19.x.x) instead of the routable proxy network (e.g., mcp-global-network). Fix: add the label in docker-compose.yml and recreate the container.

Related

• traefik-multi-network-backend-picks-wrong-ip
• traefik-multi-network-container-backend-routing-failure
• traefik-multi-network-container-backend-resolution
• docker
• traefik-multi-network-label-causes-504-on-recreate
• traefik-multi-network-container-requires-explicit-network-la
• traefik-multi-network-missing-label-routes-wrong-ip
• traefik-multi-network-missing-label-picks-wrong-backend-ip
• traefik-multi-network-container-missing-label-gotcha
• docker-iptables-bypasses-ufw-docker-user-chain-required