docker / machine

Machine management for a container-centric world
https://docs.docker.com/machine/
Apache License 2.0
6.63k stars 1.96k forks source link

Docker Machine command failed: create virtualbox (RPCServerDriver) #3131

Open eestein opened 8 years ago

eestein commented 8 years ago

My environment:

screen shot 2016-03-01 at 07 41 08

Whenever I try to run kitematic I get this error:

Command failed: /usr/local/bin/docker-machine -D create -d virtualbox --virtualbox-memory 2048 default, Docker Machine Version: 0.6.0, build e27fb87, Found binary path at /usr/local/bin/docker-machine, Launching plugin server for driver virtualbox, Plugin server listening at address 127.0.0.1:53422, () Calling .GetVersion,connection is shut down, Client () with RPCServerDriver does not work, re-attempting with RpcServerDriver, () Calling .GetVersion,connection is shut down,

I tried with versions 0.5.6 as seen here https://github.com/docker/toolbox/issues/401 and 0.6.0 more recently (as you can see on the error above).

As directed by @jeffdm I'm posting here. Any ideas on how to solve this? It's become a "huge" problem because I can only work using docker on my Parallels VM... I need to run Parallels, Windows, VS, Kitematic and so forth just because it's not working on my mac.

Similar reference #2615

/cc @sandcastle

fsoppelsa commented 8 years ago

Looks like VirtualBox is unreachable.

eestein commented 8 years ago

@fsoppelsa any ideas on how to solve it?

fsoppelsa commented 8 years ago

Can you create VMs in VirtualBox?

eestein commented 8 years ago

Yup, just check it here:

screen shot 2016-03-01 at 12 16 25

nathanleclaire commented 8 years ago

Do you have any unusual network configuration?

Does attempting such a docker-machine command manually act differently?

eestein commented 8 years ago

@nathanleclaire

1 - VPN? No 2 - Proxy? No 3 - Firewall? Only the Mac one, but I've tried turning it off and still doesn't work 4 - Antivirus? No 5 - (m)DNS server? No 6 - What's your /etc/hosts file look like?

MacBook-Pro:claims-app eestein$ cat /etc/hosts
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1   localhost
255.255.255.255 broadcasthost
::1             localhost
fe80::1%lo0     localhost

192.168.25.150  SteinWin
192.168.25.150  vm

7 - What's the output for ifconfig on your computer?

MacBook-Pro:claims-app eestein$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    options=3<RXCSUM,TXCSUM>
    inet6 ::1 prefixlen 128 
    inet 127.0.0.1 netmask 0xff000000 
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
    nd6 options=1<PERFORMNUD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    ether 60:f8:1d:b9:79:96 
    inet6 fe80::62f8:1dff:feb9:7996%en0 prefixlen 64 scopeid 0x4 
    inet 192.168.25.5 netmask 0xffffff00 broadcast 192.168.25.255
    inet6 2804:7f2:80:efa4::4 prefixlen 128 dynamic 
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active
en1: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
    options=60<TSO4,TSO6>
    ether 72:00:07:73:4e:e0 
    media: autoselect <full-duplex>
    status: inactive
en2: flags=963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX> mtu 1500
    options=60<TSO4,TSO6>
    ether 72:00:07:73:4e:e1 
    media: autoselect <full-duplex>
    status: inactive
p2p0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2304
    ether 02:f8:1d:b9:79:96 
    media: autoselect
    status: inactive
awdl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1484
    ether be:52:c1:d9:09:17 
    inet6 fe80::bc52:c1ff:fed9:917%awdl0 prefixlen 64 scopeid 0x9 
    nd6 options=1<PERFORMNUD>
    media: autoselect
    status: active
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    options=63<RXCSUM,TXCSUM,TSO4,TSO6>
    ether 62:f8:1d:9b:01:00 
    Configuration:
        id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
        maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
        root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
        ipfilter disabled flags 0x2
    member: en1 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 5 priority 0 path cost 0
    member: en2 flags=3<LEARNING,DISCOVER>
            ifmaxaddr 0 port 6 priority 0 path cost 0
    nd6 options=1<PERFORMNUD>
    media: <unknown type>
    status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
    inet6 fe80::a1f4:6622:28dc:411%utun0 prefixlen 64 scopeid 0xe 
    nd6 options=1<PERFORMNUD>

Does attempting such a docker-machine command manually act differently? No, I've actually tried that a couple of times but it's always the same outcome. Let me know if you need any more information.

Thanks!