-
Notifications
You must be signed in to change notification settings - Fork 2k
Hyperv/Windows10 - Error creating machine: Error in driver during machine creation: exit status 1 #2267
Comments
Exactly the same here! |
I currently work around the problem by:
James |
Confirmed, W10 & HyperV |
I'm seeing this on windows 8.1 with HyperV as well |
Same problem on a Windows 2012 R2 cluster |
I did some test with --debug. I think the problem is that Set-VMDvdDrive and Add-VMHardDiskDrive return before the operation is actually done since the commands just queues up the operation in the hyper-v service queue. What needs to be added is a loop that calls Get-VM and look for "Operating normally" in the status. Then when the status is 'normal', call Start-VM |
This was fixed from Docker Machine v0.5.5 onwards |
Can you reference the patch that fixed this? I had this issue running docker-machine and not with docker-compose. |
There is no reference to the issue number on the Machine 0.5.5 release notes. If you look on the release notes, it is mentioned. "Close handle after copying boot2docker.iso into vm folder - will otherwise keep hyper-v from starting vm" (Compose was a mistake which I corrected in previous comment. I meant Machine) |
This is fixed in 1cd6a37 |
I'm using docker-machine v0.7.0 and it still persists. :( Here's the debug output of create command:
|
even after maxxing memory out, it doesn't work :( My machine has 4GB... is that a limitation? |
@mrcaron
|
Same issue |
Does anyone found the solution ? |
@ronyrun not yet... still in limbo 👎 |
same here |
I found my problem is lacking of memory |
Cycling the Windows Management Instrumentation service fixed the issue for me (Windows 10). |
Running docker-machine -D start vmname show you the error. Mine was lack of memory... Added RAM to host VM and everything ran fine after... |
After run
|
On Windows 10 with Hyper V driver, I receive "Error creating machine: Error in driver during machine creation: exit status 1" most of the time. Occasionally, it succeeds but I can find nothing reliable to make it succeed every time.
The new VM fails to start when instructed by the Docker Hyper V driver. I can always start it manually successfully but then the certificates are invalid in docker for the VM because it never completed the creation.
Windows Event Log for Hyper V Worker shows:
Microsoft Emulated IDE Controller (Instance ID 83F8638B-8DCA-4152-9EDA-2CA8B33039B4): Failed to Power on with Error 'The process cannot access the file because it is being used by another process.' (0x80070020). (Virtual machine ID 4F21E751-1C17-462E-B659-97BD9FBE2783)
and
Failed to open attachment 'C:\Users\user.docker\machine\machines\dockerhost1\boot2docker.iso'. Error: 'The process cannot access the file because it is being used by another process.' (7864368). (Virtual machine ID 4F21E751-1C17-462E-B659-97BD9FBE2783)
The ISO file is not mounted by the system or any other VM.
I have disabled antivirus and indexing for the entire docker folder and confirmed that neither are causing the lock by using Process Monitor.
This was installed using Docker Toolbox 1.9.0b. I never had this problem with the previous version of Docker.
Client:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: windows/amd64
Server:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: linux/amd64
Thanks
James
The text was updated successfully, but these errors were encountered: