docker, docker compose, docker-machine, and lazydocker for OS X 10.9. The daemon runs in a Linux VM (VMware Fusion 8); docker-machine manages it.
Install VMware Fusion, then bring the Docker VM up once:
docker-machine-bootstrapIt creates the VM from the bundled image (first run only, ~1-2 min in a Terminal),
starts it, and points a docker context named mavericks at it — so docker,
docker compose, and lazydocker just work in any shell, with no environment
variables to set. docked IMAGE CMD runs a container with $PWD at /work/.
To start the VM automatically at login:
launchctl load -w /Library/LaunchAgents/dev.modernmavericks.container-tools-machine.plistThe package updates itself, and after each update offers to roll your VM onto the new image — nothing to run by hand.
- If
dockersays "cannot connect," the VM is stopped — rundocker-machine-bootstrap(or start it from the menu bar) and retry. - Migrating from an older setup? Remove any
eval "$(docker-machine env …)"or hardcodedDOCKER_HOST=line from your shell profile — it overrides the managed context. The bootstrap will notify you if it finds one. - The VM appears in VMware Fusion as "container-tools"; adjust CPU/RAM in its Settings.
- Upgrading from an older install that had a
defaultVM? Rundocker-machine-ctl migrateonce (with the VM stopped) to rename it tocontainer-tools, preserving your data. - boot2docker.iso: https://github.com/dragonflylee/boot2docker/