using alpine for pipelines fails

[sustbmat]

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

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

[sustbmat · Accepted solution]

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.

[Jeroen De Raedt]

Hey @sustbmat,

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. 

[sustbmat]

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