Bitbucket Pipelines apt-get stopped working

[DanyloVolokh]

Hi guys,

I have my Bitbucket pipelines set up for quite a while but just recently it stopped working when I try to run "apt-get" command

+ apt-get update

Get:1 http://security.debian.org jessie/updates InRelease [44.9 kB]

Ign http://deb.debian.org jessie InRelease

Ign http://deb.debian.org jessie-updates InRelease

Ign http://deb.debian.org jessie-backports InRelease

Get:2 http://deb.debian.org jessie Release.gpg [2420 B]

Ign http://deb.debian.org jessie-updates Release.gpgIgn http://deb.debian.org jessie-backports Release.gpg

Get:3 http://deb.debian.org jessie Release [148 kB]

Ign http://deb.debian.org jessie-updates Release

Ign http://deb.debian.org jessie-backports Release

Err http://deb.debian.org jessie-backports/main amd64 Packages Get:4 http://security.debian.org jessie/updates/main amd64 Packages [822 kB]

Get:5 http://deb.debian.org jessie/main amd64 Packages [9098 kB]

Err http://deb.debian.org jessie-updates/main amd64 Packages 404 Not Found

Err http://deb.debian.org jessie-backports/main amd64 Packages 404 Not FoundFetched 10.1 MB in 7s (1395 kB/s)

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages 404 Not Found

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-backports/main/binary-amd64/Packages 404 Not Found

E: Some index files failed to download. They have been ignored, or old ones used instead.

[DanyloVolokh · Accepted solution]

Ok. I have the answer.

I've changed the docker image from

image: java:8

To

image: openjdk:8

[Сергей Егоров]

Hi. The same. 
Any idea to solve the issue? 

I have a simple config:

branches:
    master:
        - step:
              script:
                  - apt-get update

+ apt-get update
Get:1 http://security.debian.org jessie/updates InRelease [44.9 kB]
Ign http://deb.debian.org jessie InRelease
Get:2 http://deb.debian.org jessie-updates InRelease [7340 B]
Get:3 http://deb.debian.org jessie Release.gpg [2420 B]
Get:4 http://deb.debian.org jessie Release [148 kB]
Get:5 http://security.debian.org jessie/updates/main amd64 Packages [825 kB]
Get:6 http://deb.debian.org jessie/main amd64 Packages [9098 kB]
Fetched 10.1 MB in 7s (1364 kB/s)

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry 'main/binary-amd64/Packages' in Release file (Wrong sources.list entry or malformed file)

E: Some index files failed to download. They have been ignored, or old ones used instead.

[Deleted user]

+1 

This happened to us over the weekend as well. The package exists and is reachable to other VM's: https://packages.ubuntu.com/cosmic/amd64/jq/download

However, when referenced via the pipeline, it routes to an unavailable CDN node: 

http://cdn-fastly.deb.debian.org/debian/dists/jessie-updates/main/binary-amd64/Packages

We are currently blocked from development as a result. Any advice?