Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Pipeline RUN apt-get update error Edited

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 jessie InRelease
Get:1 jessie-updates InRelease [7340 B]
Get:2 jessie/updates InRelease [44.9 kB]
Get:3 jessie Release.gpg [2420 B]
Get:4 jessie Release [148 kB]
Get:5 jessie/updates/main amd64 Packages [825 kB]
Get:6 jessie/main amd64 Packages [9098 kB]Fetched 10.1 MB in 30s (328 kB/s)
W: Failed to fetch

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


1 answer

1 accepted

0 votes
Answer accepted

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:

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?



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!

Like Philip Hodder likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket Pipelines

Bitbucket Pipelines Runners is now in open beta

We are excited to announce the open beta program for self-hosted runners. Bitbucket Pipelines Runners is available to everyone. Please try it and let us know your feedback. If you have any issue...

758 views 15 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you