Pipeline with apt update started to fail

[Matt Bielawski]

We started receiving the below error end of last week from the apt update step. Note our pipeline didn't change:

+ apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Ign:1 http://deb.debian.org/debian stretch InRelease
Ign:2 http://security.debian.org/debian-security stretch/updates InRelease
Ign:3 http://deb.debian.org/debian stretch-updates InRelease
Err:4 http://deb.debian.org/debian stretch Release
404 Not Found [IP: 146.75.34.132 80]
Err:5 http://deb.debian.org/debian stretch-updates Release
404 Not Found [IP: 146.75.34.132 80]
Err:6 http://security.debian.org/debian-security stretch/updates Release
404 Not Found [IP: 146.75.34.132 80]
Reading package lists...
E: The repository 'http://deb.debian.org/debian stretch Release' does not have a Release file.
E: The repository 'http://deb.debian.org/debian stretch-updates Release' does not have a Release file.
E: The repository 'http://security.debian.org/debian-security stretch/updates Release' does not have a Release file.

Our pipeline was running successfully prior to last week. Below is a snippet of our pipeline. Has anyone encountered this issue and resolved it?

- step:
image: maven:3.6.1
caches:
- maven
name: Build and Run Unit Tests
script:
- cp settings.yaml $BITBUCKET_CLONE_DIR/src/main/resources/settings.yaml
- cp appSettings.yaml $BITBUCKET_CLONE_DIR/src/main/resources/appSettings.yaml
- cp settings.xml ~/.m2/settings.xml
- apt update
- apt install jq -y

[Erez Maadani · Accepted solution]

Hi @Matt Bielawski 

I think this might help: https://community.atlassian.com/t5/Bitbucket-questions/Recently-Pipeline-apt-get-update-Fails/qaq-p/2340127#M93155

[Matt Bielawski]

Hi Erez, thank you for the suggestion. We are looking to take a similar action and are still reviewing what version of maven to update to

[Matt Bielawski]

What we found is that is that Debian 9/stretch moved to archive.debian.org
For a short term solution:
We will point apt to the archived version by adding the following line before the apt update line in our pipeline:
echo "deb http://archive.debian.org/debian stretch main" > /etc/apt/sources.list

We found this solution here: https://unix.stackexchange.com/questions/743839/apt-get-update-failed-to-fetch-debian-amd64-packages-while-building-dockerfile-f

For our Long term solution:
We will look for a newer version of the maven image that supports an updated version of apt