Problems with APT in the standard Docker image

[reitzig]

I run a "standard" job which currently fails due to problems with apt.

Log excerpts:

$ sudo apt-get update
<snip>
Fetched 21.5 kB in 3s (5,589 B/s)
Reading package lists... Done
W: GPG error: http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.4 Release: The following signatures were invalid: KEYEXPIRED 1515625755
W: The repository 'http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.4 Release' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: http://ppa.launchpad.net/couchdb/stable/ubuntu/dists/trusty/Release.gpg: Signature by key 15866BAFD9BCC4F3C1E0DFC7D69548E1C17EAB57 uses weak digest algorithm (SHA1)

$ sudo apt-get -y install fish
<snip>
Err:1 http://us-central1.gce.archive.ubuntu.com/ubuntu trusty/universe amd64 xsel amd64 1.2.0-2
  503  Service Unavailable [IP: 35.192.35.27 80]
<snip>
E: Failed to fetch http://us-central1.gce.archive.ubuntu.com/ubuntu/pool/universe/x/xsel/xsel_1.2.0-2_amd64.deb  503  Service Unavailable [IP: 35.192.35.27 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
The command "sudo apt-get -y install fish" failed and exited with 100 during .
Your build has been stopped.

There seem to be two separate issues here, but the first (the expired key) doesn't seem to be critical (here). Unavailable APT repositories. however, are.

I could reproduce the 503 shortly thereafter in a browser (the message said something about high load). A few minutes later it seems to be fine.

Can/should Travis be more robust against such errors? Should you maybe cache APT repository calls? They must be hit hard by all the CI images downloading packages over and over again...

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 7 days. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please respond before the issue is closed, or open a new one after. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues