it seems that vboxmanage start can fail and we don't detect it

[SvenDowideit]

vboxmanage is not returning an error - unless we hand parse its output :(

eg, create with an invalid serial pipe path on windows.

longer term we need to look at parsing the output, for now, call vbox status in cmdUp

[steeve]

what about the exit status code ?

[SvenDowideit]

exactly - its saying 'yup, everything is ok'

[steeve]

sigh well, shit—
Steeve Morin

On Thu, Jun 5, 2014 at 8:29 AM, Sven Dowideit notifications@github.com
wrote:

exactly - its saying 'yup, everything is ok'

Reply to this email directly or view it on GitHub:
#139 (comment)

[SvenDowideit]

I've also just had VBoxManage tell me there are no vm's (VBoxManage list vms) even though the GUI shows 2 running, and then after I stop them in the GUI, I need to boot2docker init - which succeeds! and then when I boot2docker run, it works, but the GUI still sees wherever it was before.

And.... YES, I DID accidentally run one as root and the other as a user.

and guess what, the last one started over-rides the other's port natting.

this stuff is crazy.

[tianon]

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).