You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
Docker for Windows Community Edition 18.03.0-ce-win59 2018-03-26 successfully installed on a clean Virtual machine running Windows 10 Pro Version 1709 (OS Build 16299.125). With firewall turned off and with exposed virtualization extensions.
When trying to set up a swarm, running command "docker-machine create -d hyperv --hyperv-virtual-switch "myswitch" myvm1" results in:
"This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.
SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually :2376), may not work properly.
You may need to add the route manually, or use another related workaround.
This could be due to a VPN, proxy, or host file configuration issue.
You also might want to clear any VirtualBox host only interfaces you are not using."
Docker for Windows Community Edition 18.03.0-ce-win59 2018-03-26 successfully installed on a clean Virtual machine running Windows 10 Pro Version 1709 (OS Build 16299.125). With firewall turned off and with exposed virtualization extensions.
When trying to set up a swarm, running command "docker-machine create -d hyperv --hyperv-virtual-switch "myswitch" myvm1" results in:
"This machine has been allocated an IP address, but Docker Machine could not
reach it successfully.
SSH for the machine should still work, but connecting to exposed ports, such as
the Docker daemon port (usually :2376), may not work properly.
You may need to add the route manually, or use another related workaround.
This could be due to a VPN, proxy, or host file configuration issue.
You also might want to clear any VirtualBox host only interfaces you are not using."
Note: Before running into this issue, I ran into another issue: "Hyper-V PowerShell Module is not available" so I downloaded a previous version of docker-machine.exe and replaced C:\Program Files\Docker\Docker\resources\bin\docker-machine.exe with the newly downloaded file.
The text was updated successfully, but these errors were encountered: