Is it possible to backport this to trusty too? This bit us hard, and
there are a lot of people out there posting this problem but with no
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
apt-get update hangs when apt-transport-https is not installed
Status in apt package in Ubuntu:
Status in apt source package in Xenial:
Status in apt package in Debian:
When "apt-get update" is run on a docker container running Ubuntu
v16.04 and containing an additional apt source repository hosted on an
https webserver, the "apt-get update" command hangs.
The hang happens after connections to http ubuntu hosts are complete,
and apt-get remains stuck on "Working" at 0%. Removing the sources
file for the https repo causes apt-get to complete normally.
The source file contains 4 separate entries to 4 different repos on
the same https server. When the source file is modified so that just
*one* entry exists to one repo on the https server, we suddenly get a
sensible error message that tells us that apt-transport-https needs to
Installing apt-transport-https into the docker container before adding
the sources list to the https servers works around the problem and
- The use of docker isn't related to the bug, except that the docker
image doesn't contain the apt-transport-https package whereas our
cloud images do contain this package by default. This can give the
impression that this is a docker bug when it's not.
- The hang in "apt-get update" seems to occur when the sources file
contains more than one entry in the file. When just one entry exists
in the file (and all other entries are commented out) a sensible error
- We encountered this on a host that didn't support cut and paste,
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~touch-packages
Post to : email@example.com
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp