Docker Community Forums

Share and learn in the Docker community.

Failed to create VM "MobyLinuxVM": Cannot find an overload for "min" and the argument count: "2"

docker
beta

(Abowen) #1

Expected behavior

Docker should start and I can execute “docker” commands

Actual behavior

Docker “Failed to start”, and reports the following error

Unable to execute Start: Failed to create VM “MobyLinuxVM”: Cannot find an overload for “min” and the argument count: “2”. at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Information

Diagnostic ID : 265EECB0-F59B-4DA4-8F2C-C37B6500759B/2016-07-12_10-06-20

Host : Windows 10 64 bit, 8GB RAM, i5 4590

Logs :

[10:01:18.300][PowerShell ][Info ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso…
[10:01:18.870][HyperV ][Info ] Using existing Switch: DockerNAT
[10:01:19.187][HyperV ][Info ] Using existing Switch IP address
[10:01:20.350][HyperV ][Info ] Using existing: MobyLinuxVM
[10:01:20.435][NamedPipeServer][Error ] Unable to execute Start: Failed to create VM “MobyLinuxVM”: Cannot find an overload for “min” and the argument count: “2”. at System.Management.Automation.Interpreter.ThrowInstruction.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
[10:01:20.435][NamedPipeClient][Error ] Unable to send Start: Failed to create VM “MobyLinuxVM”: Cannot find an overload for “min” and the argument count: “2”.
[10:01:20.451][NamedPipeClient][Info ] Sending CheckInstallation()…
[10:01:20.451][NamedPipeServer][Info ] CheckInstallation()

Steps to reproduce the behavior

  1. Uninstalled Docker for Windows
  2. Restarted PC
  3. Installed Docker for Windows (tried both 1.12.0-rc2 & 1.12.0-rc3)
  4. Upon startup, the above error is returned

Used a registry cleaner & deleted orphan files but made no change.


(Abowen) #2

It turns out that I had two entries in my Hyper-V Manager (virtmgmt.msc)

I deleted the two entries and deleted the existing ISO from that folder

C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks\MobyLinuxVM.vhdx

It now installed correctly.


(Murven) #3

I had the same behavior.

Removing one of the entries in Hyper-V manager let docker start again.


(Michael Friis) #4

@abowen @murven I just wanted to follow up on this - was this because you already had a MobyLinux virtual machine in hyper-v manager, or you had two?


(Murven) #5

I installed Docker.
I checked Hyper-V and there was one VM.
A couple of days later an update was released.
I installed the update.
Docker stopped working after the next computer restart.
I checked Hyper-V and there were two VMs with the same name.
I deleted one of them.
Docker started working again.

I hope this is helpful.


(Abowen) #6

It had listed two in my case.


(Ruloweb) #7

Hi all, I had the same issue, there was like 5 MobyLinux VMs, dont know why, I didnt install any new version, maybe a Windows update?

Deleting 4 of them make it work, thanks!


(Rahilwazir) #8

It still appears to throw the same error, after deleting the existing .vhdx file and VM from Hyper-V Manager.