Docker on OSX: How to start boot2docker in one shell and use it in another Docker on OSX: How to start boot2docker in one shell and use it in another docker docker

Docker on OSX: How to start boot2docker in one shell and use it in another


if boot2docker is on your path in each shell, then you can

eval "$(boot2docker shellinit)"

as per https://github.com/boot2docker/boot2docker/blob/master/README.md#tls-support


First check that the VM is ok to run as far as VT being enabled goes - a surefire way to do this is just to open Virtualbox manually (yes, not very "docker" of me... humph!) and find the VM.

Sidebar:If you mistakenly ran boot2docker init as root or another user you will see those entries in there too... remove the unneeded VMs?

Anyways, look at settings for your boot2docker-vm and see if there is a "hint" at the bottom of the settings window letting you know if something is not configured right.

Like, for instance if VT-d isnt enabled, or something like you don't have the right amount of RAM allocated for the VM or the VM's video card.

Next, start the VM from within Virtualbox.

For me, after I properly adjusted memory settings the last issue was:

VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).

So I looked here:

sudo sysctl -a | egrep VMXmachdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 CX16 TPR PDCM SSE4.1 XSAVE

So, if you have VMX show up here then you need to enable it in your bios (hackintosh) or you can enable it by updating your EFI firmware or through some other absurd method:

https://communities.vmware.com/message/932263