Pipeline RUN apt-get update error

[JT]

I keep getting this error on bitbucket pipelines on one of my branches. This only happens on that branch and not on the other branches which uses the same DockerFile. 

I also built the image in my local machine and this does not happen. Not sure what action I should take for this to be resolved. 

both happening in node: 8.11.1 and node:10.15.3

Help. :( 

Step 9/13 : RUN apt-get update ---> Running in 200b3cedbae6
Ign http://deb.debian.org jessie InRelease
Get:1 http://deb.debian.org jessie-updates InRelease [7340 B]
Get:2 http://security.debian.org jessie/updates InRelease [44.9 kB]
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 30s (328 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.
The command '/bin/sh -c apt-get update' returned a non-zero code: 100

[Philip Hodder · Accepted solution]

Hi John,

I'm not sure why this is localised onto a specific branch, but this looks like an apt-get issue that we discuss a work around for here: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Bitbucket-Pipelines-Apt-get-update-returning-404/ba-p/1042290

In your instance, I think you can try updating your Docker image to use one of the supported node tags. Such as 8.15. 10.15.3 should be working. Can you confirm that the issues is also occurring on that image?

Thanks,

Phil

[JT]

Hi Philip,

I only updated the bitbucket-pipelines.yml to use node:10.15.3. My bad.

The dockerfile was still in 8.11.1. I used node:10.15.3 instead and the pipelines ran successfully!

Thank you very much for your advice and answer!