Clean up lots of images at once (in this case where they have no name) with:

$ docker images | grep ‘<none>’ | awk ‘{print $3}’ | xargs docker rmi

You can build up these from the left by adding each piped command one at a time.

No space left on volume

If you have cleaned up old containers and you are still get `no space left on volume` when building, pulling or running, you can increase the size of boot2dockers volume. The official instructions are good, just follow them step by step: https://docs.docker.com/articles/b2d_volume_resize/

boot2docker won’t start

If you get this message:

error in run: Failed to start machine “boot2docker-vm”: exit status 1

you can often fix the issue by starting via VirtualBox.

First, open the VirtualBox app (/Applications/VirtualBox) and start the `boot2docker-vm` with the `start` button or run the following to start boot2docker with a head:

$ VirtualBox —startvm boot2docker-vm

Note: this will open a window with the boot2docker display output and will keep the terminal process so you will need to open another terminal for the next command.

Second, stop the boot2docker process using the boot2docker cmd:

$ boot2docker stop

This will close the boot2docker window and the previous terminal process will exit.

Third, start the boot2docker process using the boot2docker cmd:

$ boot2docker start

For me, this (combined occasionally with an OS X reboot) has always fixed the issue.

I forgot to use —rm when I did docker exec

You can run this to see all the containers started with exec:

$ docker ps -a —no-trunc | grep ‘ “/exec ‘ | sed ‘s/ */\ /g’

StreamOutputError: image not found

If you see something like this when running `docker pull` or `docker run`:

compose.progress_stream.StreamOutputError: Error: image <repo/image:tag> not found

it could be because you have a typo in the repo name, but it could also be because the repo is private and you haven’t run `docker login` yet. Just type