Boot2docker fails to start virtual machine - fail to bind socket, VERR_NOT_SUPPORTED OS X

[bheavner]

I'm attempting to get boot2docker running on my work computer. I'm logged in to the computer running OS X version 10.9.5 with a user account that mounts the home directory from the office network.

goldfinger:~ bheavner$ boot2docker up -v Using virtualbox driver 2014/10/08 14:27:20 executing: VBoxManage showvminfo boot2docker-vm --machinereadable 2014/10/08 14:27:21 executing: VBoxManage startvm boot2docker-vm --type headless Waiting for VM "boot2docker-vm" to power on... VBoxManage: error: NamedPipe#0 failed to bind to local socket /home/bheavner/.boot2docker/boot2docker-vm.sock (VERR_NOT_SUPPORTED) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole 2014/10/08 14:27:22 executing: VBoxManage showvminfo boot2docker-vm --machinereadable error in run: Failed to start machine "boot2docker-vm" (run again with -v for details)

[bheavner]

I updated to the most recent VirtualBox (4.3.16 r95972), and get the same result.

[bheavner]

Using the VirtualBox Manager, if I change the settings on the VM to disable the serial port, it appears to work fine. So... problem managed for me, but I'm not sure if this requires a change to make it easier for future people who come across the problem.

[SvenDowideit]

very very surprising - You're the first person that has reported an issue with it. @tianon given that we're now adding virtualisation specific stuff to the iso's, perhaps you could turn the serial port code off, as we're not going to persuade MS and VMWare to use it instead..

[tianon]

Oh bizarre. Yeah, I'd be +1 on getting rid of the serial port stuff by default.