boot2docker-vm setup fails due to DYLD_LIBRARY_PATH settings

[mmontag]

I downloaded the OS X installer. I'm running OS X 10.8.5 and VirtualBox 4.3.12.

My boot2docker-vm is not starting due to DYLD stuff in my environment. Seems to be an old problem for VBoxManage.
Here's what I see for boot2docker init -v:

montag:~ $ boot2docker init -v
2014/06/09 17:11:10 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/06/09 17:11:10 Creating VM boot2docker-vm...
2014/06/09 17:11:10 executing: VBoxManage list vms
2014/06/09 17:11:10 executing: VBoxManage createvm --name boot2docker-vm --register
Virtual machine 'boot2docker-vm' is created and registered.
UUID: 4e832fce-2c78-46ac-a551-79de869e0351
Settings file: '/Users/montag/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vbox'
2014/06/09 17:11:10 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/06/09 17:11:10 Apply interim patch to VM boot2docker-vm (https://www.virtualbox.org/ticket/12748)
2014/06/09 17:11:10 executing: VBoxManage setextradata boot2docker-vm VBoxInternal/CPUM/EnableHVP 1
2014/06/09 17:11:10 executing: VBoxManage modifyvm boot2docker-vm --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 8 --memory 1024 --vram 8 --acpi on --ioapic on --rtcuseutc on --cpuhotplug off --pae on --longmode on --synthcpu off --hpet on --hwvirtex on --triplefaultreset off --nestedpaging on --largepages on --vtxvpid on --vtxux off --accelerate3d off --uart1 0x3F8 4 --uartmode1 server /Users/montag/.boot2docker/boot2docker-vm.sock --boot1 dvd
2014/06/09 17:11:11 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/06/09 17:11:11 Setting NIC #1 to use NAT network...
2014/06/09 17:11:11 executing: VBoxManage modifyvm boot2docker-vm --nic1 nat --nictype1 virtio --cableconnected1 on
2014/06/09 17:11:11 executing: VBoxManage controlvm boot2docker-vm natpf1 ssh,tcp,127.0.0.1,2022,,22
2014/06/09 17:11:11 Port forwarding [ssh] tcp://127.0.0.1:2022 --> :22
2014/06/09 17:11:11 executing: VBoxManage controlvm boot2docker-vm natpf1 docker,tcp,127.0.0.1,2375,,2375
2014/06/09 17:11:11 Port forwarding [docker] tcp://127.0.0.1:2375 --> :2375
2014/06/09 17:11:11 executing: VBoxManage list hostonlyifs
2014/06/09 17:11:11 executing: VBoxManage list dhcpservers
2014/06/09 17:11:11 Creating a new host-only network interface...
2014/06/09 17:11:11 executing: VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
2014/06/09 17:11:11 executing: VBoxManage hostonlyif ipconfig dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp --ip 192.168.59.3 --netmask 255.255.255.0
VBoxManage: error: The host network interface with the given name could not be found
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component Host, interface IHost, callee nsISupports
VBoxManage: error: Context: "FindHostNetworkInterfaceByName(name.raw(), hif.asOutParam())" at line 218 of file VBoxManageHostonly.cpp
VBoxManage: error: Could not find interface 'dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp'
2014/06/09 17:11:11 Failed to create host-only network interface: exit status 2

I worked around the issue by doing

unset DYLD_LIBRARY_PATH
unset LD_LIBRARY_PATH

before boot2docker init.

Seems others calling VBoxManage have had to work around this issue as well - hashicorp/vagrant#1258.

[SvenDowideit]

I'm putting this unset in the OSX installer - perhaps we should also work it into the b2d-cli utils.cmd() :(

[SvenDowideit]

see boot2docker/osx-installer#38

[fabriziogiudici]

Is this supposed to be part of 1.3.2? Because I'm seeing it failing...

[localhost:~] fritz% boot2docker -v init
Boot2Docker-cli version: v1.3.2
Git commit: e41a9ae
2014/11/25 19:36:56 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/11/25 19:36:56 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/11/25 19:36:56 executing: VBoxManage list vms
2014/11/25 19:36:56 executing: VBoxManage createvm --name boot2docker-vm --register
Virtual machine 'boot2docker-vm' is created and registered.
UUID: d5ce80f0-c6f1-42ee-b78e-f9e002f65c7d
Settings file: '/Users/fritz/Business/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vbox'
2014/11/25 19:36:56 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/11/25 19:36:56 executing: VBoxManage setextradata boot2docker-vm VBoxInternal/CPUM/EnableHVP 1
2014/11/25 19:36:56 executing: VBoxManage modifyvm boot2docker-vm --firmware bios --bioslogofadein off --bioslogofadeout off --natdnshostresolver1 on --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 8 --memory 2048 --vram 8 --acpi on --ioapic on --rtcuseutc on --cpuhotplug off --pae on --longmode on --synthcpu off --hpet on --hwvirtex on --triplefaultreset off --nestedpaging on --largepages on --vtxvpid on --vtxux off --accelerate3d off --uart1 0x3F8 4 --uartmode1 server /Users/fritz/.boot2docker/boot2docker-vm.sock --boot1 dvd
2014/11/25 19:36:56 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/11/25 19:36:56 executing: VBoxManage modifyvm boot2docker-vm --nic1 nat --nictype1 virtio --cableconnected1 on
2014/11/25 19:36:56 executing: VBoxManage controlvm boot2docker-vm natpf1 ssh,tcp,127.0.0.1,2022,,22
2014/11/25 19:36:56 executing: VBoxManage list hostonlyifs
2014/11/25 19:36:56 executing: VBoxManage list dhcpservers
2014/11/25 19:36:56 executing: VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
2014/11/25 19:36:56 executing: VBoxManage hostonlyif ipconfig dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp --ip 192.168.59.3 --netmask 255.255.255.0
VBoxManage: error: The host network interface with the given name could not be found
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component Host, interface IHost, callee nsISupports
VBoxManage: error: Context: "FindHostNetworkInterfaceByName(name.raw(), hif.asOutParam())" at line 218 of file VBoxManageHostonly.cpp
VBoxManage: error: Could not find interface 'dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp'
error in run: Failed to initialize machine "boot2docker-vm": exit status 2

[SvenDowideit]

@fabriziogiudici ah, excellent - I was unable to test my change, as I don't know how to get my OSX to have this problem.

If you can work out how to make it happen for one of us devs, then we can try to work out how to fix it

or more ideally, perhaps you can check out the code and have a go yourself. :)

[fabriziogiudici]

I'll try but I don't promise anything... I don't know Go.

But in the meantime... is there any way to manually fix the VM that was being created? What was trying to do boot2docker-cli? Was it the last thing that it was trying to do?

[fabriziogiudici]

Ok, it seems my problem is different and I've casually found a workaround :-)

That's what I did: rename VBoxManage to VBoxManage.orig and create a bash script named VBoxManage:

#!/bin/bash

echo "============================: ARGS $@" >> $TMPDIR/VBoxManage.log
printenv >> $TMPDIR/VBoxManage.log

VBoxManage.orig "$@"
exit $?

The idea was to find a quick way to check the env passed to VBoxManage. First, what I see is that DYLD_LIBRARY_PATH and LD_LIBRARY_PATH are empty, so they are correctly managed. But I found a problem with my script because my VirtualBox workspace is in a directory with a space in the path: /Users/fritz/VirtualBox VMs: because of that I experienced an earlier failure when creating the disks. So I worked with my script and "$@" seems to be the correct way to manage it. At this point... everything seems to work :-) I mean: there's still something I don't understand, as I don't see in the log the offending command dealing with the network management; but what I see is that boot2manage -v init completed correctly and I could execute boot2manage up and boot2manage ssh (before doing that, I commented out the echo and printenv, just in case the stdout of VBoxManage is processed).

Thus I'd rather say that the problem might be with the space in the VirtualBox workspace path. Does this suggest something to you?

[bossjones]

I was able to reproduce as well:

OS X 10.8.5.

VirtualBox workspace path = /Users/malcolmjones/VirtualBox VMs

Perhaps it has to do with the space in the path like @fabriziogiudici mentioned? ( good work debugging btw ! )

○ → boot2docker -v init
Boot2Docker-cli version: v1.3.2
Git commit: e41a9ae
2014/12/03 09:24:19 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/12/03 09:24:19 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/12/03 09:24:19 executing: VBoxManage list vms
2014/12/03 09:24:19 executing: VBoxManage createvm --name boot2docker-vm --register
Virtual machine 'boot2docker-vm' is created and registered.
UUID: f8c43808-03b2-4cd2-aaf4-6f215de00b30
Settings file: '/Users/malcolmjones/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vbox'
2014/12/03 09:24:19 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/12/03 09:24:19 executing: VBoxManage setextradata boot2docker-vm VBoxInternal/CPUM/EnableHVP 1
2014/12/03 09:24:19 executing: VBoxManage modifyvm boot2docker-vm --firmware bios --bioslogofadein off --bioslogofadeout off --natdnshostresolver1 on --bioslogodisplaytime 0 --biosbootmenu disabled --ostype Linux26_64 --cpus 8 --memory 2048 --vram 8 --acpi on --ioapic on --rtcuseutc on --cpuhotplug off --pae on --longmode on --synthcpu off --hpet on --hwvirtex on --triplefaultreset off --nestedpaging on --largepages on --vtxvpid on --vtxux off --accelerate3d off --uart1 0x3F8 4 --uartmode1 server /Users/malcolmjones/.boot2docker/boot2docker-vm.sock --boot1 dvd
2014/12/03 09:24:19 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2014/12/03 09:24:19 executing: VBoxManage modifyvm boot2docker-vm --nic1 nat --nictype1 virtio --cableconnected1 on
2014/12/03 09:24:19 executing: VBoxManage controlvm boot2docker-vm natpf1 ssh,tcp,127.0.0.1,2022,,22
2014/12/03 09:24:19 executing: VBoxManage list hostonlyifs
2014/12/03 09:24:19 executing: VBoxManage list dhcpservers
2014/12/03 09:24:19 executing: VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
2014/12/03 09:24:19 executing: VBoxManage hostonlyif ipconfig dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp --ip 192.168.59.3 --netmask 255.255.255.0
VBoxManage: error: The host network interface with the given name could not be found
VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component Host, interface IHost, callee nsISupports
VBoxManage: error: Context: "FindHostNetworkInterfaceByName(name.raw(), hif.asOutParam())" at line 218 of file VBoxManageHostonly.cpp
VBoxManage: error: Could not find interface 'dyld: DYLD_ environment variables being ignored because main executable (/Applications/VirtualBox.app/Contents/MacOS/VBoxNetAdp'
error in run: Failed to initialize machine "boot2docker-vm": exit status 2

[SvenDowideit]

ping @tianon I presume fixing some space in paths escaping issue is possible...