Reporting wrong IP address on Win2016 with Containers

The following screenshot shows the SSM agent reporting a misleading IP address for managed instances running AMI `Windows_Server-2016-English-Full-Containers-2016.11.09`. The reported IP address is that of the internal Docker NIC rather than the expected instance IP. See also attached `ipconfig` output.

```
Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : ap-southeast-2.compute.internal
Link-local IPv6 Address . . . . . : fe80::c953:eeef:a09:6818%5
IPv4 Address. . . . . . . . . . . : 10.130.16.64
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.130.16.1

Ethernet adapter vEthernet (HNS Internal NIC):

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::34cd:72e2:43db:a2b8%2
IPv4 Address. . . . . . . . . . . : 172.26.192.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
```

Start by reproducing the report on AMI Windows_Server-2016-English-Full-Containers-2016.11.09 and compare the SSM agent's reported address with the attached ipconfig output. Trace how the agent selects the instance IP versus the Docker HNS Internal NIC, and consider the issue done when it consistently reports the expected instance address.

Written by the indexing model from the issue text.