The problem is that you still need VirtualBox AND Linux. I don't see how this is lighter weight...other than a 24MB image instead of a 160MB image.
Hmm this replaces Vagrant (which I know and like) with a custom script (<a href="https://raw.github.com/steeve/boot2docker/master/boot2docker" rel="nofollow">https://raw.github.com/steeve/boot2docker/master/boot2docker</a>) which I have to learn.<p>Also running docker on a non-ubuntu host means you're doing it differently than 95% of people out there, so you'll be on your own when it comes to mysterious errors and the like.<p>In case you're feeling brave, here's an anecdote from just this morning. My colleague ran into a mysql bug on docker he couldn't figure out. Googling the error messsage + "docker" instantly produced this page <a href="http://stackoverflow.com/questions/21026790/cant-delete-mysql-database-table-or-even-alter-table-inside-docker" rel="nofollow">http://stackoverflow.com/questions/21026790/cant-delete-mysq...</a> where it was explained that by using ubuntu 13.10 instead of 12.04 would make the problem go away... saving us many hours of further debugging. What good would that advice do if we were using TinyCore Linux?
My lightweight experience is a little different. I didn't want to run a VM on my MacBook Air and I already run VMs locally on my Mac Mini so an alias to the Ubuntu VM on my mini lets me run the Docker client without anything else on my Air.<p>alias docker='docker -H=tcp://10.0.5.3:5555'<p>A DynDNS + NAT rule on my router lets me connect when I'm not home.