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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,218
Community Members
 
Community Events
176
Community Groups

Pipeline failing without error message

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

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

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

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

this saved my day :D thanks

Like Sander de Kroon likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events