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

using alpine for pipelines fails

We have used alpine as the base image for our lightweight pipelines checks for few months without a problem.

However 2 days back all the pipelines jobs started failing with following error: "rpc error: code = Unknown desc = no supported platform found in manifest list"
There's a link to documentation and link to pipelines config validation.

This has happened in multiple separate repositories. There were no changes to the bitbucket-pipelines.yml for weeks.

Configuration is valid. Here's one example:

image: alpine

- step:
name: YAML lintian
- apk -q --no-progress --no-cache add py2-pip
- pip -q install yamllint
- yamllint -c .yamllint templates/



1 answer

1 accepted

This is updated based on the comment information.

Alpine docker image available at Docker Hub was missing the manifest and it wasn't possible to use it.

Issue at Alpine Github

This can be prevented by version pinning in your bitbucket-pipelines configuration file by specifying concrete version of docker image that is known to run.

Kudos to @Jeroen De Raedt for clearing this up!


Everything seems to work now - assuming a temporary problem.

It's interesting that at the time the BB status page was reporting all green.

Hey @Matěj Šusta,

we were also affected by this. It turns out that the alpine image on DockerHub got updated and was in a broken state. It has been fixed now, which explains why your builds works again. 

Rather than relying on the latest, we now depend on a previous stable version. 

Thanks for clearing this up!

Here is the Alpine issue in Github

I'm probably going to stay without the pinning. There should not be that many major issues in a major branch when they have separate edge channel. Hopefully.
Would like to stay current and not have to update all the pipelines configuration files for updates...

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...

993 views 20 11
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