Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Pipeline failing without error message

Sander de Kroon January 20, 2022

Our pipeline keeps on failing without giving a reason why.

 

Schermafbeelding 2022-01-20 om 15.15.20.png

 

It certainly has something to do with our custom Docker image, but I cannot figure out what exactly. Whenever I try another public image, the pipeline runs just fine. But if I use our own, it fails on the build step.

 

The Docker image: https://hub.docker.com/r/sudwestfryslan/default-pipeline

bitbucket-pipelines.yml

image:
name: sudwestfryslan/default-pipeline
username: $DOCKER_HUB_USERNAME
password: $DOCKER_HUB_PASSWORD
email: $DOCKER_HUB_EMAIL
pipelines:
default:
- step:
script:
- php --version
- npm --version

 

What I have tried:

  • Changing to another public image -> Works! Unfortunately, that's not a solution as I want to use a custom image.
  • Include the tag in the image name (e.g. :latest or :php74) -> makes no difference
  • Include the complete URL to the docker registry -> makes no difference
  • Include/exclude docker credentials -> makes no difference

 

Right now I'm kind of stuck, as I do not know what error is occurring.

1 answer

0 votes
Oleksandr Kyrdan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 28, 2022

Hi @Sander de Kroon

Thank you for your question!

Have you tried to move custom docker image usage to the step and add service: - docker parameter?

image:
name: atlassian/default-image:3

pipelines:
default:
- step:
image: sudwestfryslan/default-pipeline
script:
- php --version
- npm --version
service:
- docker

 

Also, try to test your custom docker image locally with command and make sure that it works correctly: 

docker run -it sudwestfryslan/default-pipeline

 

Best regards,
Oleksandr Kyrdan

Sander de Kroon January 28, 2022

I have tested the image locally and it works :). But it did turn out that my local machine was the 'problem' so to speak.

 

I'm on a mac with a M1 processor. This, by default, produces ARM images. And apparently these do not work on the Pipelines.

 

For anyone encountering the same issue, I've written a short blogpost about it here https://sanderdekroon.xyz/blog/bitbucket-pipelines-docker-and-the-apple-m1-chip/

Like # people like this
Oleksandr Kyrdan
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 28, 2022

@Sander de Kroon Thank you for sharing your solution and contributing to the community.

Vytautas Stankus June 29, 2022

this saved my day :D thanks

Like Sander de Kroon likes this
Advitum January 2, 2024

I spent way to long debugging this problem, until I found this thread.

Sanders Blog is gone, but for anyone having the same problem, the blog post can be restored here: http://web.archive.org/web/20230926025303/https://sanderdekroon.xyz/blog/bitbucket-pipelines-docker-and-the-apple-m1-chip/

Sander de Kroon January 3, 2024

I've restored the blog post :)

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events