Build started failing at apt-get step

Build Environment
1

No changes done on our end, just started breaking last night.

sudo apt update && sudo apt-get install libxml2-utils libgtk2.0-0 libgtk-3-0 libgbm-dev libnotify-dev libgconf-2-4 libnss3 libxss1 libasound2 libxtst6 xauth xvfb

now fails with:

0% [Working]Ign:1 http://deb.debian.org/debian stretch InRelease
0% [Waiting for headers]Ign:2 http://deb.debian.org/debian stretch-updates InRelease
0% [Waiting for headers]Err:3 http://deb.debian.org/debian stretch Release
  404  Not Found
0% [Waiting for headers]Err:4 http://deb.debian.org/debian stretch-updates Release
  404  Not Found
0% [Waiting for headers]Ign:5 http://security.debian.org/debian-security stretch/updates InRelease
0% [Working]            Err:6 http://security.debian.org/debian-security stretch/updates Release
  404  Not Found
0% [Working]Reading package lists... Done
E: The repository 'http://deb.debian.org/debian stretch Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://deb.debian.org/debian stretch-updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://security.debian.org/debian-security stretch/updates Release' does no longer have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Exited with code exit status 100
CircleCI received exit code 100

Thanks!

1 Like
2

Could you provide details about the environment you are running including which image you are working with as the errors are being generated within the image’s OS environment, rather than the CircleCI environment.

3

@rit1010 of course, is this what you’re looking for?

orbs:
  cypress: cypress-io/cypress@1
docker:
      - image: circleci/node:12.22.7
      - image: mongo:4.2.6
4

Working with circleci/node:12.22.7 may be causing you issues. This image was last updated by CircleCI back in Oct 2021 and from the errors you have listed debian.org may have modified the underlying repos. It may also just be that the repos are suffering an issue and waiting a while will see the issue go away.

If the issue does not clear up on its own the best answer would be for you to raise a support ticket so that your issue can be passed on to the team that maintains the image. While the image has not be built/reissued for some time, it does not mean that it is not supported.

1 Like
5

Thanks! I just created a support ticket, hopefully they can help.

6

Hey,

Did you get any follow-up? I have the same issues but with a different image.

Thanks.

1 Like
7

No, not yet. But I’ll post here once I do.

8

Hi,
I have the same problème on streamlit.
An other forum speak about it on streamlit forum (I cant send link…).

The post name :
E: The rRepository ‘security debian org debian-security stretch updates Release’ no longer has a Release file

9

experiencing the same here

10

Hi ! I have the same problem with

docker:
      - image: circleci/node:14.17.1
11

Reply I just got from the support:

I had a look at your config and see that you are using a legacy image: circleci/node:12.22.7.
 
We have deprecated the circleci images in favor of our next-gen cimg images. The error is caused by outdated references in the legacy image's apt source list because Debian has recently made updates on how their file structuring works.
 
We recommend that you update your image to use the equivalent convenience image:
- https://circleci.com/developer/images/image/cimg/node

I guess I’ll try to use that cimg image and hope I can get it to work with that :crossed_fingers:

12

My build is working again :tada:
Changing circleci/node:12.22.7 to cimg/node:12.22.7 was all I needed to do.

3 Likes
13

use, change circleci for cimg, and now is work again.

Example:

Old, legacy Image:

  • circleci/node:14.17.1

New, next-gen Image:

  • cimg/node:14.17.4

Remember check the available Tags in the cimg/node info page.

2 Likes
14

I am using
docker:
- image: circleci/buildpack-deps:stretch
Do i also need to change this image?

15

I am facing same issue as
debian-security stretch/updates InRelease

0% [Waiting for headers]

Ign:2 debian stretch InRelease

0% [Waiting for headers]

Ign:3 debian stretch-updates InRelease

0% [Waiting for headers]

Err:4 debian-security stretch/updates Release
404 Not Found

0% [Waiting for headers]

Err:5 debian stretch Release

16

If you’re using an image which is not available in cimg e.g circleci/node:8.9-stretch, you can just add following commands before apt-get update

sudo sed -i s/deb.debian.org/archive.debian.org/g /etc/apt/sources.list
sudo sed -i 's|security.debian.org|archive.debian.org/debian-security/|g' /etc/apt/sources.list 
sudo sed -i '/stretch-updates/d' /etc/apt/sources.list
sudo apt-get update
2 Likes
17

Thank you!!!

A slightly modified version worked for me:

sudo sed -i s/deb.debian.org/archive.debian.org/g /etc/apt/sources.list
sudo sed -i 's|security.debian.org|archive.debian.org|g' /etc/apt/sources.list
sudo sed -i '/stretch-updates/d' /etc/apt/sources.list
18

Thank you! My image, circleci/ruby:2.6.6-stretch-node-browsers had another sources list, so I had to do:

sudo sed -i s/deb.debian.org/archive.debian.org/g /etc/apt/sources.list
sudo sed -i s/deb.debian.org/archive.debian.org/g /etc/apt/sources.list.d/stretch-backports.list
sudo sed -i 's|security.debian.org|archive.debian.org|g' /etc/apt/sources.list
sudo sed -i '/stretch-updates/d' /etc/apt/sources.list
19

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.