Pipeline pulls docker image but not work
Asked by ferpaxecosanxez:

Hello team,

I am testing public docker images and this is my case:

I pulled in my local public image "[atlassian/default-image:4](https://hub.docker.com/layers/atlassian/default-image/4/images/sha256-07b4477486e0ff88680da7435fdf927f9841bb78f642b121bd6cd2e54d88a9b1?context=explore)", I tag and I push in my public DockerHub "[s4gconsulting/bitbucket](https://hub.docker.com/layers/s4gconsulting/bitbucket/latest/images/sha256-3519248da477be88a1f402fa4b8f33e1c62715fa97f6166d3e4c31906a5e6547?context=explore)", in other words, the same image with different name within my public DockerHub.

Well, i have the next YML that pointing Atlassian public DockerHub:  

```
## Depth to clone project
clone:
  depth: full

## Use S4G image to manage Salesforce code
image:
  name: atlassian/default-image:4

pipelines:
  default:
    - step:
        name: Validate Docker Image 
        script:
          - echo "Public image OK"
```

The result with this public image is **OK**, and has the same code SHA

![Screenshot 2023-04-05 at 09.48.09.png](https://community.atlassian.com/t5/image/serverpage/image-id/249911i464485DA53E175F1/image-size/large?v=v2&px=999 "Screenshot 2023-04-05 at 09.48.09.png")

Now, I want use my public Docker image, which is a copy from "atlassian/default-image:4", so, my updated YML is:

```
## Depth to clone project
clone:
 depth: full

## Use S4G image to manage Salesforce code
image:
 name: s4gconsulting/bitbucket:latest

pipelines:
 default:
   - step:
       name: Validate Docker Image 
       script:
         - echo "Public image OK"
```

The public image was pulled (code SHA is right), but the result is **ERR**:

![Screenshot 2023-04-05 at 09.26.51.png](/t5/image/serverpage/image-id/249909i4FD21230960FE84D/image-size/large?v=v2&px=999 "Screenshot 2023-04-05 at 09.26.51.png")

If the public images are pulled for each pipeline:

* Why the second pipeline fails?
* Why the second pipeline cannot run: echo "Public image OK"?

Please, help ?


Answers:
author: Mark C
body: Hi [@ferpaxecosanxez](/t5/user/viewprofilepage/user-id/5187993),

Thank you for reaching out to the community.

The reason why your Pipelines build is failing while using the custom Docker image (s4gconsulting/bitbucket:latest) is that it was built using **linux/arm64** architecture.  

For comparison, you can check the following links and notice the "OS/ARCH" field:

* [s4gconsulting/bitbucket](https://hub.docker.com/layers/s4gconsulting/bitbucket/latest/images/sha256-3519248da477be88a1f402fa4b8f33e1c62715fa97f6166d3e4c31906a5e6547?context=explore)
* [atlassian/default-image](https://hub.docker.com/layers/atlassian/default-image/4/images/sha256-07b4477486e0ff88680da7435fdf927f9841bb78f642b121bd6cd2e54d88a9b1?context=explore)

Unfortunately, we do not officially support ARM images on Bitbucket Cloud Pipelines infrastructure at the moment.  
We do have an existing feature request for it that can be located through this link. - <https://jira.atlassian.com/browse/BCLOUD-15317>  
You can upvote and watch it for now so that you'll be notified of any updates from our team when the feature becomes available on Bitbucket Cloud.

For now, you can rebuild your custom Docker image and use **linux/amd64** architecture instead.

Hope it helps and let me know how it goes.

Regards,  
Mark C

comments: author: ferpaxecosanxez
body: Hi [@Mark C](/t5/user/viewprofilepage/user-id/1210823),

Indeed, when generating an image with the **linux/amd64** architecture, everything works correctly.

As a suggestion, that error could be reported by pipeline logs like: *Currently the architecture "linux/arm64" is not supported*.

Thank you very much ?


Tags: bitbucket-cloud

bitbucket-pipelines

cloud

docker

yml