Closed DongyueWang closed 7 years ago
You're probably missing --hyperv-virtual-switch
. See this: https://github.com/docker/labs/blob/master/swarm-mode/beginner-tutorial/swarm-node-hyperv-setup.ps1
Could I ask you to please close and re-open this on the docker-machine repo? https://github.com/docker/machine/
the hyperv-virtual-switch is DockerNAT which is internal net type. should I create a virtual switch of external net type ?
2017-02-12 16:58 GMT+01:00 Michael Friis notifications@github.com:
You're probably missing --hyperv-virtual-switch. See this: https://github.com/docker/labs/blob/master/swarm-mode/ beginner-tutorial/swarm-node-hyperv-setup.ps1
Could I ask you to please close and re-open this on the docker-machine repo? https://github.com/docker/machine/
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/489#issuecomment-279227753, or mute the thread https://github.com/notifications/unsubscribe-auth/ALXIGrtImTvoNvs4NPIhFO21K4P9wmyOks5rbyw8gaJpZM4L-fUG .
Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.
If you have found a problem that seems similar to this, please open a new issue.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle locked
Expected behavior
Waiting for machine to be running, this may take a few minutes... Detecting operating system of created instance... Waiting for SSH to be available... Detecting the provisioner... Provisioning with boot2docker... Copying certs to the local machine directory... Copying certs to the remote machine... Setting Docker configuration on the remote daemon... Checking connection to Docker... Docker is up and running! To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env manager
Actual behavior
Setting Docker configuration on the remote daemon...
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. Checking connection to Docker... Docker is up and running! To see how to connect your Docker Client to the Docker Engine running on this virtual machine, run: docker-machine env manager
Information
Steps to reproduce the behavior