Driver overlay failed to create image

[redthor]

Hi @nickjj

I'm getting the following when attempting to build the docker containers in the VM (chapter 8).

Sending build context to Docker daemon 10.24 kB
Step 0 : FROM python:2.7.10-slim
Pulling repository docker.io/library/python
4175166f8ecc: Error pulling image (2.7.10-slim) from docker.io/library/python, Driver overlay failed to create image rootfs 7c5108a910f47faa7233ae47f9ae4c0ae29a7d3856364e37e92cd063b624f4e9: lstat /var/lib/docker/overlay/1d6f63d023f51ae1bbc8c5623bcde3de05751dbe9bba5ae4b3405005f8b856c9: no such file or directory b3405005f8b856c9: no such file or directory 
21845f98d5b6: Download complete 
7c5108a910f4: Error downloading dependent layers 
Error pulling image (2.7.10-slim) from docker.io/library/python, Driver overlay failed to create image rootfs 7c5108a910f47faa7233ae47f9ae4c0ae29a7d3856364e37e92cd063b624f4e9: lstat /var/lib/docker/overlay/1d6f63d023f51ae1bbc8c5623bcde3de05751dbe9bba5ae4b3405005f8b856c9: no such file or directory
Restarting rediscounter
Error response from daemon: no such id: rediscounter
Error: failed to stop containers: [rediscounter]

I think it might be this: https://github.com/docker/docker/issues/9718

I'm going to try and upgrade docker inside CoreOS (currently Docker version 1.8.3, build cedd534-dirty) and see if that fixes it.

Registering here in case any of your readers get the same issue.

[nickjj]

Thanks, I didn't come across this because back when I made the book that version of Docker didn't have the bug.

Hopefully 1.9 fixes it and that CoreOS's beta channel gets updated soon. Let's leave this open until CoreOS has the fixed version of Docker.

[redthor]

I tried to upgrade docker in CoreOS but it didn't appear trivial. Instead I switched from the beta channel to the stable channel for CoreOS (in the Vagrantfile) and that seems to have sorted it out.

[nickjj]

At some point beta is going to shift into stable, so hopefully that issue gets resolved before it does.

As of making this comment, stable is still running Docker 1.7.1. At least you were able to resolve this for now.

[nickjj]

@redthor The more simple fix seems to be just downgrading to python:2.7.9-slim in the Dockerfile until whatever is busted on Docker's side is fixed.

[redthor]

ok, thanks. Swapping to stable CoreOS is also pretty easy for the moment.