Apt-get update fails only on some containers, but works on others?


#1

We are splitting up our tests by running a subset of them on different containers via the parallelization features that CircleCI providers. As of today (2019-01-31), we’ve been getting apt-get update errors on some of the containers.

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb  404  Not Found [IP: 91.189.88.149 80]

is the error that we are getting. This feels like an issue with CircleCI for a couple reasons:

  • we haven’t changed my CircleCI config in a while
  • only 1/4 containers fail, the rest apt-get update just fine

#2

We are seeing the same issue.


#3

This is usually caused by Ubuntu mirror issues and is out of our control, but we’ll keep an eye out for any further information or trends we can act on.


#4

It’s been happening all day for us. I’ve looked around for a solution, but haven’t came up with much. Is switching to a different mirror a possible solution?


#5

This AskUbuntu post and answer explains how to change your mirrors, and includes a list of options. Maybe that will help.

It may be a little tricky being on a CI platform to edit that file, but you may be able to use sed, to edit the file, as explained here https://unix.stackexchange.com/a/335847/125837

You can add that as a step prior to calling apt-get

EDIT: It looks like the security repo is failing for you, I’m not sure if there are mirrors for that :frowning:


#6

This answer to set the number of retries for Apt may be a better option https://askubuntu.com/questions/875213/apt-get-to-retry-downloading