I have had this issue as well. I believe it's because of a recent update to either boot2docker or Virtualbox. In any case, the solution is to just to temporarily route until it is fixed upstream.

First, open virtualbox and check the network settings on the boot2docker vm to see what the host only adapter is named. In my case, it's vboxnet1; for you, it may be vboxnet0.

Then, apply this command:

sudo route -nv add -net 192.168.59 -interface vboxnet1

Now you should be able to run docker commands.

See  for more information