Wrong IP after certain VMs boot about mech HOT 5 CLOSED

This issue is undoubtedly the single most annoying issue I run into with mech. If I install docker inside of a virtual machine, vmrun will no longer find the IP address correctly and you end up having to go into Fusion to get the actual IP address

❯ mech up
Bringing machine up...
Getting IP address...
Sharing current folder...
VM started on 172.17.0.1

from mech.

I was checking how this is done in Vagrant, it seems it also suffers from the same problem, they had/have (hashicorp/vagrant#6580) and they added enable_vmrun_ip_lookup, which must be using a script to get the IP, somehow. I wonder how they’re doing it...

from mech.

This problem was getting annoying so I looked into it.

        vmrun.user = 'vagrant'
        vmrun.password = 'vagrant'
        vmrun.runScriptInGuest('/bin/sh', "hostname -I > /tmp/ip_address")
        with tempfile.NamedTemporaryFile() as fp:
            vmrun.copyFileFromGuestToHost('/tmp/ip_address', fp.name)
            fp.seek(0)
            ip_addresses = fp.read()
            if ip_addresses:
                print(ip_addresses.split()[0])

This code works although the hostname man page says we can't rely on its order for output. Perhaps a better way is to use a more advanced command or test the IPs?

from mech.

I don't like my current approach (changes to getGuestIPAddress), do you think this should be a change in vmrun or higher in mech/utils?

from mech.

I implemented an enable_ip_lookup as of e77d319

from mech.