Docker 1.7.0 issues: problems with Mac and boot2docker, ARM, Ubuntu, and disk size of images

Docker 1.7.0 has been released into the wild. Every .0 release of software should be expected to have some issues, no matter how good the QA and automated test process. Here's what to expect if you're getting Docker 1.7.0 up and running.

boot2docker on Mac

On the Mac, with boot2docker: Docker certs not valid with 1.7 upgrade is issue 938 on boot2docker. The symptom is a message like this

An error occurred trying to connect: Get https://192.168.59.103:2376/v1.19/containers/json: x509: certificate is valid for 127.0.0.1, 10.0.2.15, not 192.168.59.103

and restarting docker on the VM with boot2docker ssh sudo /etc/init.d/docker restart fixes it, at least temporarily. Read through the issue on github to see the full diagnosis - as best I understand it, eth1 is not up when certificates are generated, hence the cert not valid error.

Raspberry Pi or any other ARM system

On a Raspberry Pi: Docker 1.7 on RaspberryPI : "socket operation on non-socket" is issue 14184 on docker. The symptom is a message like this:

[tki@anzu ~]$ docker start redis Error response from daemon: Cannot start container redis: socket operation on non-socket Error: failed to start containers: [redis]

The error flushed out a whole set of people running Docker on ARM on a variety of platforms, all having similar issues. If you're running a Scaleway C1, ODROID C1, ODROID XU3-Lite, Utilite Pro, Cubox 4x4, and all flavors of Raspberry Pi or Pi 2 you'll see this. "When using --net host the container starts" is the report, but port forwarding fails to work in that case.

Ubuntu: problems with statically compiled Docker binaries

The issue is Ubuntu 15.04 vivid can not start docker 1.7.0, docker issue 14035. The relevant bits of the error message are

ERRO[0000] Udev sync is not supported. This will lead to unexpected behavior, data loss and errors. For more information, see https://docs.docker.com/reference/commandline/cli/#daemon-storage-driver-option

ERRO[0000] [graphdriver] prior storage driver "devicemapper" failed: driver not supported

FATA[0000] Error starting daemon: error initializing graphdriver: driver not supported

There is a long discussion, culminating in In the end, removing /var/lib/docker/devicemapper/ will fix the issue, but people are also rolling back to 1.6.2.

Ubuntu on x86: large file sizes

A report that Docker 1.7.0 is using huge amounts of disk space appears on the Docker forum, item 2046. Pulling image fills disk/image size is huge, version 1.7.0 is issue 14204 on Docker. Not much insight into this one yet.