- Containers can access only host and neighbor containers, external network is not accessible.
- Containers have network connectivity for few seconds after restart.
- Containers are configured in host-routed mode. Switching to bridged mode helps to avoid the problem.
- Teaming is configured on the node, and teaming type is "Smart Load Balancing".
Network connectivity loss is caused by ARPs sent from all active interfaces of the Teamed adapter, therefore when external host tries to access the container in most cases reverse-path check produces a failure, and packets are being dropped causing network connectivity issues for the containers.
Due to this nature of "Smart Load Balancing" this mode is not supported.
Configure your Teaming Adapters to use "Link Aggregation" or "Generic Trunking" modes.
If some Teaming adapter on the node is not used for container's traffic (in example - teaming for iSCSI) - it may work in SLB mode.
NOTE: Windows 2008 R2, 2008, and 2003 do not have native support for network link aggregation and teaming, This is implemented by NIC drivers, therefore the instructions for reconfiguration vary for different NIC manufacturers. Please check the documentation respectively.