-
Notifications
You must be signed in to change notification settings - Fork 2k
Waiting for host to start... (hyperv) #4328
Comments
I have the similar issue, except my machine starts and it never gets an IP address, even though I followed everything from docs. docker --version: Docker version 17.12.0-ce-rc3, build 80c8033 This is on edge, same thing happens on stable. Although, I noticed I can't run windows containers for some reason, so it looks like something is wrong with my current setup. docker-machine --debug -d "hyperv" --hyperv-virtual-switch "BridgedConnection" worker3
|
@knilecrack |
Did you mean this ? https://1drv.ms/u/s!AtmVXevYpYur6j6WHvexC6ShiqkO |
Don't know really. ¯_(ツ)_/¯ I'll close the issue until the problem arises again. |
Hi everybody and happy new year. I followed correctly instructions of this page Microsoft Hyper-V My setup
What can I do to resolve this problem ? |
@rifton007 |
start with --debug option and paste output. |
hey, if you still have issue, try setting IP address manually in VM. 1st get subnet of the switch by right-clicking on adapter that you are trying to use for VM, choose status and then details and you will see a network and subnet of the switch. Then you can try to assign an IP from that subnet on the machine. Connect to a VM from hyperv, and then just type: let me know if that worked for you, you can check by |
I also encountered this issue, and fixed it, I think the root cause is: the document is unclear. |
@timothy2005 Thanks for you efforts. 👍 Added link to your solution to the top. |
@hinell Thanks a lot! |
I am facing the same problem as @rifton007 #4328 (comment) SOLVED BY @timothy2005's #4328 (comment). Thanks.. |
It worked for me! tks |
I faced the same issue. retried from powershell window in admin mode, first vm took around 10 minutes while appeared to be stuck at Starting Vm step but eventually completed the task. second vm was created much faster. |
solve this by NOT add -hyperv-memory!At fitst i set this to 512, but when i remove this, it works. |
my way out, thanks @moviewang |
SOLVED: At first try to stop using
--hyperv-memory
cause it is fails to start up your vm even if it is adjusted via hyper-v-manager. Also, you should specify--hyperv-virtual-switch
explicitly to allow docker to connect properly. If it still doesn't work then try to remove virtual switch bridge manually via windows network adapters settings and create it once again by using hyper-v manager.See also another solution below
Hangs on when I'm creating new virtual machine.
I followed several similar issues for virtualbox like #3826 but with no luck.
Setup
windows 10 x64
boot2docker
- v17.11.0-cedocker
- 17.11.0-ceVirtual switch is enabled via Hyper-V manager as described here
Steps to reproduce
1 Install docker & Enable hyper-v feature in windows features
2 Enable Virtual Switch
3
$ docker-machine create -d hyperv --hyperv-memory 512 vm1
4 Hangs forever
I also tried to use
--debug
flag with the same command and got this (clickable) output:user/.docker/machine/cache/boot2docker.iso
and create vm again but didn't help. The machine hangs anyway.The text was updated successfully, but these errors were encountered: