Pipeline apt-get update Fails

[Carlos Agsoto]

Here is my Pipeline file 

# This is a sample build configuration for JavaScript.
# Check our guides at https://confluence.atlassian.com/x/14UWN for more examples.
# Only use spaces to indent your .yml configuration.
# -----
# You can specify a custom docker image from Docker Hub as your build environment.
image: node:10.9.0
pipelines: 
branches: 
master: 
- step: max-time: 10 
name: production 
deployment: production 
caches: 
- node 
- ncftp 
script: # Modify the commands below to build your repository. 
- npm install 
- npm install -g @angular/cli@7.3.3 
- ng build --prod 
- apt-get clean 
- apt-get update 
- apt-get install ncftp 
- ncftpput -v -u $FTP_USERNAME -p $FTP_PASSWORD -R $FTP_HOST $FTP_SITE_ROOT dist/* 
- echo Finished uploading files to $FTP_HOST$FTP_SITE_R
definitions: caches: ncftp: /var/cache/apt node: node_modules

This is the error I am getting 

+ 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 8s (1182 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.

This was working a couple of day ago but now it failing. Any help on solving this issue would be much appreciated.   

[Philip Hodder]

Hello,

Docker images based off Debian Jessie no longer perform apt-get update successfully.

We have full details documented here: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Bitbucket-Pipelines-Apt-get-update-returning-404/ba-p/1042290

You can likely just upgrade your Docker image to a new version to fix the issue. 10.9.0 is no longer a support tag (which is why it wasn't updated to fix this issue), but you can use node:10.9.0-stretch if you don't want to upgrade your node version. Otherwise I suggest you use a supported node tag documented here: https://hub.docker.com/_/node

Thanks,

Phil