Failure during apt-get update command

Feedback & Bug Reports
,
1

Over the weekend we started receiving failures when running sudo apt-get update. Here are the two images it’s running on and it looks like we could potentially add this argument (--allow-releaseinfo-change) to the command to get it to move forward. However, it doesn’t seem like the most prudent thing to do for every build.

What needs to be done to adjust our build in order to allow this command to succeed?

  • image: circleci/clojure:openjdk-11-lein-2.9.5
  • image: circleci/postgres:11.1-ram
#!/bin/bash -eo pipefail
sudo apt-get update
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists... Done      
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '10.9' to '10.10'
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Exited with code exit status 100
CircleCI received exit code 100
2

Have encountered this same problem with our builds, and have the exact same question - is there action needed in our build scripts, or is this similar to Build fails on apt-get update and CircleCI will fix this and it will “just start working again” soon?

I believe this is related to Debian 10 “buster” being superceded by Debian 11 “bullseye” yesterday

3

I came across this older article that might be relevant for those looking for paths forward before we hear back from CircleCI on this (solution #4 looks like a decent workaround for now, for example): Build fails on 'apt-get update' command – CircleCI Support Center

4

I heard back from support about a couple other solutions too:

  • use the namespace cimg instead of circle, which they are switching to and has newer versions of their images
  • the latest patch versions of an image may have a more recent update in them that will let this work (but this may require upgrading your language version to that patch version first)
5

Hi folks! As @jcw kindly pointed out, the circleci images are now legacy images and in maintenance mode. Moving forward please use the cimg images. This isn’t always as direct as replacing circleci with cimg, but you can find the images you require here:

https://circleci.com/developer/images

There is also a manual workaround here, by adding the following step before any other apt commands:

sudo apt-get --allow-releaseinfo-change-suite update

Thanks!
Al