Docker 2.7.10 image issue about python

[oeuftete]

This affects me as well, and from discussions in the docker IRC channel, this affects anyone using docker 1.9.0, the only officially supported version per https://hub.docker.com/_/python/ . At least some other python images (I've seen 3.4.3, others report 3.5.0) have the same issue.

Edit: For anyone wanting to use 2.7 or 3.4 with docker 1.9.0, the 2.7.9 and 3.4.2 images seem to pull OK.

$ docker info; docker pull python:2.7.10
Containers: 0
Images: 489
Server Version: 1.9.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 492
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-32-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 4
Total Memory: 7.705 GiB
Name: pickens
ID: IME5:LWBY:KWHP:MHN7:JUCW:JF7O:MOY2:J3R7:22HW:FCCL:N3XE:PYCU
Username: xxxxxxxx
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Pulling repository docker.io/library/python
aff5fe6ff082: Error pulling image (2.7.10) from docker.io/library/python, endpoint: https://registry-1.docker.io/v1/, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /var/lib/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf:aff5fe6ff082: Error pulling image (2.7.10) from docker.io/library/python, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /var/lib/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf: no such file or directory 
dc921aeac8d0: Error downloading dependent layers 
dc921aeac8d0: Pulling metadata 


Error pulling image (2.7.10) from docker.io/library/python, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /var/lib/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf: no such file or directory

[nickjj]

I'm seeing this happen with Docker 1.9 too. Docker 1.8.3 is working fine with the same image on Linux but I'm not sure because I had this related issue popup the other day from someone else nickjj/deploy-web-apps-with-docker#5.

[tianon]

It looks like this might be related to moby/moby#18047 -- it's definitely an issue in the Docker Engine -> Hub interaction though, so there's not much we can do about it except hope that team figures out a good fix (and then re-push the affected images once they've got the fix in place). Sorry for the trouble! 😞

[density]

@tianon interesting. that looks like it could have been it. so are we just completely out of luck until the fix is in? is there any way to push working versions of the python images? i'm sure a lot of people who depend on this to deploy are out of luck for now

[nickjj]

I would take a peek at this too, moby/moby#18008.

I can confirm with @oeuftete that 2.7.9 and 2.7.9-slim are both working with Docker 1.8.3 (probably 1.9 too but I didn't test first hand).

@tianon one thing is for sure, please don't touch 2.7.9 until this is fixed haha.

[tianon]

I've tested again, and this seems to be working here, so I wonder if something changed on the Hub side? Can anyone else confirm?

[nickjj]

It's failing here with python:2.7.10-slim still while python:2.7.9-slimworks as it did 12 hours ago.

Tested it on a fresh Debian Jessie host running Docker 1.8.3.

[oeuftete]

I can now pull python:2.7.10 with docker 1.9.0, but not python:3.4.3:

Error pulling image (3.4.3) from docker.io/library/python, Driver aufs failed to create image rootfs dc921aeac8d06e7bd5b2d85b8684bb7c94ed08db3f18a9b6e897827810b289de: open /media/r0/var/lib/docker/aufs/layers/4c0cc976b7bbefe9abdfd8f0aae1bb3759004d3c9888c3164b38909b862c0cdf: no such file or directory

[yosifkit]

We are working to roll back the build server to docker 1.8.3 and rebuild the images; it'll take some time for it to complete.

[tianon]

This is fixed now. 👍