Ubuntu Docker images include packages deleted from trusty-updates

[Mark Henwood]

Steps to reproduce (using a docker container):

$ docker pull ubuntu:trusty

$ docker run --rm -it ubuntu:trusty /bin/bash

# lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04

# apt-get update

# apt-get install python3.4
python3.4 is already the newest version.

# python3 --version
Python 3.4.3

# dpkg -l python3.4
ii python3.4 3.4.3-1ubuntu1~14.0

# apt-get install apache2
...

# apt-get install libapache2-mod-wsgi-py3
The following packages have unmet dependencies:
 libapache2-mod-wsgi-py3 : Depends: libpython3.4 (>= 3.4~b1) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Confirmed - I have followed your reproduction steps and hit the same issue.

The underlying reason however is not in the python3.4 nor mod-wsgi packages. The issue is that the Docker "ubuntu:trusty" image seems to include python3.4 version 3.4.3-1ubuntu1~14.04.1 from trusty-proposed but does not (and should not) have trusty-proposed enabled in sources.list. When apt later wants to install a matching libpython3.4, it cannot find it.

So this is a bug in the Docker image, which incorrectly includes packages from Ubuntu from trusty-proposed. I'll mark this Invalid against the mod-wsgi and apache2 packages in Ubuntu as there is no fix to be made in those packages. I'll add a generic Ubuntu task so we don't forget this issue until I can track down who needs to be fixing the Docker image.

[Robie Basak (racb)]

It seems that I can't create a generic Ubuntu task since other Ubuntu tasks already exist, so I'll leave this with the docker.io package for now so we don't lose it.

I think we need a Launchpad project for cloud images if we don't already have one.

[Ben Howard (utlemming)]

I am unable to repo this bug.

[Ben Howard (utlemming)]

Scratch comment #3.

[Ben Howard (utlemming)]

This was caused by Bug #1500768.

[Dan Watkins (daniel-thewatkins)]

Hi Mark, all,

At some point, Python 3.4.3 was released to the trusty archive. However, a (serious) regression was found, and it was removed from the archive. This image was built after the release, but before the removal, which means it has ended up in a state that apt-get doesn't understand.

The fix for this is simply to release a new image; I have pinged Tianon, the awesome community member who handles the Docker Ubuntu images, on IRC (and subscribed him to this bug) to make that happen. He's based on the West Coast, so the earliest we'll see this happen is in a few hours.

Apologies for the broken state that things ended up in; we strive to produce images of the highest quality, and don't like it when we fall short of that.

Thanks,

Dan

[Dan Watkins (daniel-thewatkins)]

For avoidance of doubt, this problem was caused by the actions taken to remedy bug 1500768. Workarounds to get an instance unstuck can be found there.

Dan

[Mark Henwood (mcbhenwood)]

Thank you @racb for taking the time to look into this and reassign it correctly - apols for my clumsy assignment.

Dan @daniel-thewatkins - thanks dude.