Skip to content
This repository was archived by the owner on Feb 27, 2018. It is now read-only.
This repository was archived by the owner on Feb 27, 2018. It is now read-only.

boot2docker-vm setup fails due to DYLD_LIBRARY_PATH settings #148

Closed
#324
Closed
boot2docker-vm setup fails due to DYLD_LIBRARY_PATH settings#148
#324
Assignees
tianon
Milestone
1.5.0

Description

@mmontag
mmontag
opened on Jun 10, 2014

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.

Activity

  1. SvenDowideit
    changed the title [-]boot2docker-vm setup fails[/-] [+]boot2docker-vm setup fails due to DYLD_LIBRARY_PATH settings[/+] on Jul 5, 2014

  2. SvenDowideit commented on Jul 5, 2014

    @SvenDowideit
    SvenDowideit
    on Jul 5, 2014
    Contributor

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

  3. SvenDowideit commented on Jul 10, 2014

    @SvenDowideit
    SvenDowideit
    on Jul 10, 2014
    Contributor

    see boot2docker/osx-installer#38

  4. SvenDowideit
    closed this as completedon Jul 10, 2014
  5. SvenDowideit
    added a commit that references this issue on Nov 10, 2014

    use HZ_100 as suggested by @tatsushid

    6d24fac

  6. fabriziogiudici commented on Nov 25, 2014

    @fabriziogiudici
    fabriziogiudici
    on Nov 25, 2014

    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

  7. SvenDowideit commented on Nov 26, 2014

    @SvenDowideit
    SvenDowideit
    on Nov 26, 2014
    Contributor

    @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. :)

  8. fabriziogiudici commented on Nov 26, 2014

    @fabriziogiudici
    fabriziogiudici
    on Nov 26, 2014

    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?

  9. fabriziogiudici commented on Nov 26, 2014

    @fabriziogiudici
    fabriziogiudici
    on Nov 26, 2014

    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?

  10. bossjones commented on Dec 3, 2014

    @bossjones
    bossjones
    on Dec 3, 2014

    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

  11. SvenDowideit commented on Dec 4, 2014

    @SvenDowideit
    SvenDowideit
    on Dec 4, 2014
    Contributor

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

  12. SvenDowideit
    reopened this on Dec 4, 2014
  13. SvenDowideit
    added this to the 1.4.0 milestone on Dec 4, 2014
  14. SvenDowideit
    assigned
    tianon
    on Dec 4, 2014

  15. sebgoa commented on Dec 10, 2014

    @sebgoa
    sebgoa
    on Dec 10, 2014

    Same issue here. osx 10.8.5, VB 4.3.18.r96516 and VB 4.3.20 boot2docker 1.3.2. What's weird is that I have it working on one mac, but it fails on another with the same setup. Definitely seems to be a vbox issue as I get an error when creating a host only network manually.

    Indeed Vagrant faced this way back: hashicorp/vagrant@e367a8c

    Unsetting DYLD_LIBRARY_PATH had no effect. I am still investigating.

    EDIT:
    I got it working, by closing Vbox, unsetting DYLD_LIBRARY_PATH, restarted VBox, confirmed that I could create a host only interface by hand. then the boot2docker init worked.

  16. delfuego commented on Dec 22, 2014

    @delfuego
    delfuego
    on Dec 22, 2014

    I too hit this bug; the only way I could figure out to get past it was to first go into the VirtualBox GUI and create a new VM with a host-only network interface. After that, boot2docker init happily created my new boot2docker VM.

    To note for specifics: this is a machine that never had VirtualBox on it, it was installed by the boot2docker installer. Fresh from that installation, running boot2docker -v init caused the same error as above (namely VBoxManage: error: The host network interface with the given name could not be found). By first using the GUI to manually create a new VM that had a host-only interface, I then was able to proceed with boot2docker.

    (And note that I just created the simplest VM I could, choosing "Other" and "DOS", 4 Mb RAM, no hard disk, and a host-only network interface. All of which I then deleted back out.)

  17. fjenett commented on Dec 27, 2014

    @fjenett
    fjenett
    on Dec 27, 2014

    I created a foo VM with the same settings as given above: Other / DOS / 4… . Network was set to "host-only" interface. Now boot2socker init and start worked fine.

  18. SvenDowideit
    modified the milestones: 1.5.0, 1.4.0 on Dec 30, 2014

  19. jsolis commented on Jan 7, 2015

    @jsolis
    jsolis
    on Jan 7, 2015

    Thanks @Runseb 😄 nothing except for closing VBox, unset DYLD_LIBRARY_PATH, restart, boot2docker init worked for me.

  20. lc3t35 commented on Jan 28, 2015

    @lc3t35
    lc3t35
    on Jan 28, 2015

    +1 OSX 10.8.5 VBox 4.3.20.

    boot2docker init -v
Boot2Docker-cli version: v1.4.1
Git commit: 43241cb
2015/01/28 14:09:49 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:09:49 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:09:49 executing: VBoxManage list vms
2015/01/28 14:09:49 executing: VBoxManage createvm --name boot2docker-vm --register
Virtual machine 'boot2docker-vm' is created and registered.
UUID: 67f1ebda-197d-466a-8011-96fb725d66cd
Settings file: '/Users/laurent/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vbox'
2015/01/28 14:09:49 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:09:49 executing: VBoxManage setextradata boot2docker-vm VBoxInternal/CPUM/EnableHVP 1
2015/01/28 14:09:49 executing: VBoxManage modifyvm boot2docker-vm --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --natdnshostresolver1 off --natdnsproxy1 off --ostype Linux26_64 --cpus 4 --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/laurent/.boot2docker/boot2docker-vm.sock --boot1 dvd
2015/01/28 14:09:49 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:09:49 executing: VBoxManage modifyvm boot2docker-vm --nic1 nat --nictype1 virtio --cableconnected1 on
2015/01/28 14:09:49 executing: VBoxManage controlvm boot2docker-vm natpf1 ssh,tcp,127.0.0.1,2022,,22
2015/01/28 14:09:50 executing: VBoxManage list hostonlyifs
2015/01/28 14:09:50 executing: VBoxManage list dhcpservers
2015/01/28 14:09:50 executing: VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
2015/01/28 14:09:50 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

    I succeed within VBox GUI to desactivate card 1, reactivate and choose local network, save.
    Then no more error with boot2docker init -v

    boot2docker init -v
Boot2Docker-cli version: v1.4.1
Git commit: 43241cb
2015/01/28 14:12:13 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:12:13 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:12:13 executing: VBoxManage list vms
2015/01/28 14:12:13 executing: VBoxManage createvm --name boot2docker-vm --register
Virtual machine 'boot2docker-vm' is created and registered.
UUID: 15efe6ad-68d1-4df0-8c3f-37fe47e5b38f
Settings file: '/Users/laurent/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vbox'
2015/01/28 14:12:13 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:12:13 executing: VBoxManage setextradata boot2docker-vm VBoxInternal/CPUM/EnableHVP 1
2015/01/28 14:12:13 executing: VBoxManage modifyvm boot2docker-vm --firmware bios --bioslogofadein off --bioslogofadeout off --bioslogodisplaytime 0 --biosbootmenu disabled --natdnshostresolver1 off --natdnsproxy1 off --ostype Linux26_64 --cpus 4 --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/laurent/.boot2docker/boot2docker-vm.sock --boot1 dvd
2015/01/28 14:12:13 executing: VBoxManage showvminfo boot2docker-vm --machinereadable
2015/01/28 14:12:13 executing: VBoxManage modifyvm boot2docker-vm --nic1 nat --nictype1 virtio --cableconnected1 on
2015/01/28 14:12:13 executing: VBoxManage controlvm boot2docker-vm natpf1 ssh,tcp,127.0.0.1,2022,,22
2015/01/28 14:12:13 executing: VBoxManage list hostonlyifs
2015/01/28 14:12:13 executing: VBoxManage list dhcpservers
2015/01/28 14:12:13 executing: VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
2015/01/28 14:12:13 executing: VBoxManage hostonlyif ipconfig vboxnet6 --ip 192.168.59.3 --netmask 255.255.255.0
2015/01/28 14:12:13 executing: VBoxManage list dhcpservers
2015/01/28 14:12:13 executing: VBoxManage dhcpserver add --netname HostInterfaceNetworking-vboxnet6 --ip 192.168.59.99 --netmask 255.255.255.0 --lowerip 192.168.59.103 --upperip 192.168.59.254 --enable
2015/01/28 14:12:13 executing: VBoxManage modifyvm boot2docker-vm --nic2 hostonly --nictype2 virtio --cableconnected2 on --hostonlyadapter2 vboxnet6
2015/01/28 14:12:14 executing: VBoxManage storagectl boot2docker-vm --name SATA --add sata --portcount 4 --hostiocache on --bootable on
2015/01/28 14:12:14 executing: VBoxManage storageattach boot2docker-vm --storagectl SATA --port 0 --device 0 --type dvddrive --medium /Users/laurent/.boot2docker/boot2docker.iso
Converting from raw image file="stdin" to file="/Users/laurent/VirtualBox VMs/boot2docker-vm/boot2docker-vm.vmdk"...
Creating dynamic image with size 20971520000 bytes (20000MB)...
Initializing disk with ssh keys
...
  21. gmlewis
    closed this as completedin #324on Feb 24, 2015

  22. tianon commented on Feb 24, 2015

    @tianon
    tianon
    on Feb 24, 2015
    Contributor

    Now that #324 has merged, can we get someone who can duplicate the issue to test and verify that actually unsetting the offending variables instead of just emptying them out actually does fix it? 😄

  23. gmlewis commented on Feb 24, 2015

    @gmlewis
    gmlewis
    on Feb 24, 2015
    Contributor

    I have not been able to duplicate the issue... sorry.

  24. kordless commented on Feb 25, 2015

    @kordless
    kordless
    on Feb 25, 2015

    I can confirm, using the latest versions of boot2docker (1.5.0) and virtualbox (4.3.22.r98236) that this issue persists. I did everything I found on the Internets as suggestions (reinstall, install with brew, blow away existing VMs, use VB GUI to add/delete interfaces) before stumbling upon this issue here (which ironically was just closed within the day).

    Again, the solution is to do the following:

    unset DYLD_LIBRARY_PATH
unset LD_LIBRARY_PATH

  25. nicolashery commented on Apr 7, 2015

    @nicolashery
    nicolashery
    on Apr 7, 2015

    Unsetting the DYLD_LIBRARY_PATH and LD_LIBRARY_PATH variables didn't immediately work for me. I opened the VirtualBox GUI, and removed all of the VMs there (some where "trash", i.e. I had removed them manually already). Then (with the GUI still open, but not sure if that matters), I ran boot2docker init and it worked.

    Had installed boot2docker 1.5.0 via brew and virtualbox 4.3.26-98988 via brew cask. Running OS X 10.8.5.

    Since I didn't really have a "clean slate" before doing this (had tried reinstalling, manually removing VMs etc.) before doing this, I'm not sure what effect the VirtualBox GUI had, but thought I'd post it here in case someone had this issue again.

  26. perryn commented on Apr 24, 2015

    @perryn
    perryn
    on Apr 24, 2015

    I ran into this issue with

    boot2docker 1.5.0
    VirtualBox 4.3.4

    I did not have and DYLD_ or LD_ set.

    I opened the VirtualBox GUI and then 'boot2docker init' worked.

    I then closed the VirtualBox GUI and then 'boot2docker init' still worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions