Error getting state for host using Docker Machine

[arun-gupta]

Installed Docker Machine 0.5.0 and tried listing all the existing machines using docker-machine ls. The following error message is thrown:

~ > docker-machine ls
error getting state for host lab: /usr/local/bin/VBoxManage showvminfo lab --machinereadable failed:
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), callee nsISupports
VBoxManage: error: Context: "COMGETTER(SharedFolders)(ComSafeArrayAsOutParam(folders))" at line 2186 of file VBoxManageInfo.cpp

NAME        ACTIVE   DRIVER       STATE     URL                         SWARM
cluster     -        virtualbox   Running   tcp://192.168.99.108:2376   
couchbase   -        virtualbox   Running   tcp://192.168.99.101:2376   
javaone     -        virtualbox   Running   tcp://192.168.99.109:2376   
lab         -        virtualbox   Error                                 
lab2        *        virtualbox   Running   tcp://192.168.99.112:2376   

[nathanleclaire]

Weird. Does it work on subsequent invocations or same error message?

[arun-gupta]

docker-machine ls gave that error consistently.

Removed and recreated the machine and now stuck with #2147 (comment)

[bfirsh]

I got the error when upgrading an existing install (a 1.9 RC).

$ docker-machine upgrade default                                                          !86
Stopping machine to do the upgrade...
/usr/local/bin/VBoxManage showvminfo default --machinereadable failed:
VBoxManage: error: The object is not ready
VBoxManage: error: Details: code E_ACCESSDENIED (0x80070005), component SessionMachine, interface IMachine, callee nsISupports
VBoxManage: error: Context: "COMGETTER(BandwidthControl)(bwCtrl.asOutParam())" at line 2243 of file VBoxManageInfo.cpp

Starting the machine and then upgrading again works fine - I can't reproduce now.

[dgageot]

Hi @arun-gupta, thanks a lot for the feedback. I faced the same problem today and I know how to fix it. docker-machine ls contacts the hosts in separate go routines. But vbox isn't really happy about that. I'm going to shoot a PR.