Updates November 2015
To everyone on OSX or Windows: Don’t let Boot2docker leave you with the impression that Docker sucks! It’s really just your antique OS.
- Docker is amazing, period.
- However it’s rough-around-the-edges, hackey utility, boot2docker - for OS X, Windows and old Linux Kernels - leaves a lot to be desired.
Boot2docker causes 99/100 headaches compared with using a native docker install locally. I should concede that it wraps several other complicated/flakey technologies: VirtualBox, x-platform Folder Sharing, and also the docker cli command runs in a network-client mode so, file copying, builds etc take a long time vs. running a native docker server. ============= Docker can currently only run natively on a Linux Kernel 3.4+ - and the current boot2docker vm actually runs v4. Bottom Line: Install the Latest Debian (w/ xfce or MATE) on your Mac/Windows box, … c’mon those games aren’t helping your code…
Boot2docker Key Commands
When you get error: ‘FATA’
- Full error message:
- FATA Get http:///var/run/docker.sock/v1.18/info: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?
- Solution: You need some info from boot2docker
- Run this to get the 3 needed shell environment variables:
boot2docker shellinit # Copy & paste the exports into the current shell, & retry $(docker info)
Get Docker Server IP Address
Now your app on port 3000 is available at something like: http://$(boot2docker ip):3000/
Boot2Docker Quick Start for OS X
- In a terminal on your
brew install boot2docker boot2docker init boot2docker up