$ swarmexec ui → Networks → n
The two overlay mistakes nothing else reports
Docker addresses a new overlay out of 10.0.0.0/8 and sizes it for a
1500-byte link. On a cloud private network both are wrong at once: the nodes
already live in 10.0.x.y, and the link carries 1450. Neither failure
announces itself. The first hands a container an address a node already owns; the
second drops exactly the packets too big to fit, which reads as a slow connection
rather than a broken one.
Before it creates anything, swarmexec proposes a subnet that collides with nothing — not the node addresses, not the configured underlay, not an existing network, not the swarm's default pool — and the MTU the overlay should carry. The agents report their nodes' own link MTUs, so the number is read off the wire rather than assumed.
com.docker.network.driver.mtu states the underlay's MTU and
Docker subtracts 50 bytes of VXLAN overhead from it — so writing in what you want
inside costs 50 bytes a packet and looks right. It proposes and does not
substitute: whether an overlap is acceptable is your call, but the moment after
the network exists is the moment it can no longer be changed without detaching
every service from it.
⚠ 10.0.1.0/24 contains host IPs: 10.0.1.2 (node-1), 10.0.1.3 (node-2)
⚠ frames of 1500 bytes (1450 inside the overlay) do not fit a
1450-byte underlay: the packets that exceed it are dropped
without an error
→ suggested subnet 10.40.0.0/24 — clear of 3 node address(es),
the configured underlay, 11 existing network(s)
→ set MTU 1450 (the underlay's own), which gives containers 1400 bytes
Create anyway?