Whilst alluding briefly to packet capture and analysis tools, the troubleshooting guide does not go into any detail on specific diagnostic steps which users can use to isolate faults in their container networking. Consequently, when faced with connectivity issues between containers it is not clear whether the root cause is some misconfiguration of or bug in weave itself, or a general Linux networking issue. For example, stale ARP cache entries can be a common cause of unreachability - it would be good to include documentation on use of ip neigh show and tcpdump arp so that users can satisfy themselves that weave is behaving properly in such circumstances...
Whilst alluding briefly to packet capture and analysis tools, the troubleshooting guide does not go into any detail on specific diagnostic steps which users can use to isolate faults in their container networking. Consequently, when faced with connectivity issues between containers it is not clear whether the root cause is some misconfiguration of or bug in weave itself, or a general Linux networking issue. For example, stale ARP cache entries can be a common cause of unreachability - it would be good to include documentation on use of
ip neigh show
andtcpdump arp
so that users can satisfy themselves that weave is behaving properly in such circumstances...