Troubleshooting

House cleaning of Docker old images or containers:

To see all your Docker images:

docker images

Note: Docker images are stacked, so for instance the 1.6 GB size of Voodoo already include the size of the Devstep image and the size of the Ubuntu Trusty image.

Chances are nothing is using the images without any tag. Typically when you update an image with docker pull it will leave the old image untagged occupying space.

You can remove the old untagged images with:

docker rmi $(docker images | grep "^<none>" | awk "{print $3}")

To see your running containers:

docker ps

Now by accident, some container may have been stopped without being removed. You can see all of them with:

docker ps -a

To remove all stopped Docker images (no risk for Voodoo), simply do:

docker rm $(docker ps -a -q)

Also consider rm -f option if it fails for some reason.

Docker container is already assigned

Use docker rm -f sha1 to remove the old container, for instance:

rvalyi@rvalyi-laptop:~/DEV/voodoo6$ ./ak
assuming shared Odoo directory: /home/rvalyi/.buildout/odoo8
assuming shared eggs directory: /home/rvalyi/.buildout/eggs
Entering Docker warp zone with shareds volumes:
-v /home/rvalyi/DEV/voodoo6:/workspace -v /home/rvalyi/.buildout/odoo8:/.devstep/addons/voodoo/odoo -v /home/rvalyi/.buildout/eggs:/.devstep/addons/voodoo/host_eggs
Odoo will run on port 8069
2014/09/10 10:46:14 Error response from daemon: Conflict, The name voodoo-voodoo6 is already assigned to bfeba10fbc8a. You have to delete (or rename) that container to be able to assign voodoo-voodoo6 to a container again.
rvalyi@rvalyi-laptop:~/DEV/voodoo6$ docker rm -f bfeba10fbc8a
bfeba10fbc8a

Pushing to a repo with non standard 22 port

Set up your repo remote normally. But edit your .ssh/config and set something like:

Host server_ip
HostName server_ip
Port 4019
User root