Closed steveendow closed 2 years ago
RESOLVED:
I realized that I had not rebooted the server since installing Hyper-V.
So I stopped the BC container, rebooted the Windows Server, then restarted the BC container.
I can now connect to the BC container successfully.
Thanks to a suggestion from Sebastian about trying to restart the Docker service:
https://twitter.com/sschuh365/status/1473709943819804676?s=20
My speculation is that the Hyper-V installation modified the Windows Network adapters, which caused the Docker network to stop working. Either restarting Docker or restarting Windows caused Docker to recognize the new network configuration and start working properly.
I have a Server 2019 ltsc (v1809 Build 17763.2029) machine that has been running Docker EE (Mirantis Container Runtime version 20.10.7) without issue for months.
I had to install Hyper-V to host some Windows VMs on the server, and now I am unable to connect to any BC Docker containers.
The BC containers are successfully created without any obvious errors, and they have IP address & host name entries in the hosts file, but I can't ping the container IP or connect to the container in a browser anymore using either the host name or IP address over HTTP. (I'm not using https with BC containers)
I am able to run this command which returns JSON data:
And I am also able to run this command to get a PowerShell prompt for the container:
And this command does successfully export a Windows Event Log file from the container:
When I run netstat -an, I am seeing the failed connection attempts to the container IP (172.20.143.95) with SYN_SENT status.
Did installing Hyper-V break Docker networking? Or could I have broken Docker networking when I figured a new virtual switch for my Hyper-V hosts?
Or is there something else in Docker that doesn't play well with Hyper-V on the same host?
Scripts used to create container and cause the issue
Full output of scripts
Docker Network info: