Bitbucket Runner error when using arm64 Docker images

nils_oe

We are developing software for NVIDIA Jetson modules which are ARM based. In our Bitbucket pipelines we would like to build the C++ modules using an ARM based Docker image (eg arm64v8/ubuntu or an official NVIDIA Jetson container). 

We have set up a Runner on our local infrastructure and it is working fine for x86 containers (eg using image: alpine or image: ubuntu). However, as soon as we use image: arm64v8/ubuntu instead, the Runner gives the following error: 

Status 409: {"message":"Container 8f58435f39954e35e625bc4c7d2a034de5827e1e9ae8c506bb272d3ac60d9bdf is not running"}  

Are arm based containers not supported for Runners? Are there any workarounds for this? 

Thanks a lot for any input on this!

Theodora Boudale

Hi @nils_oe,

We have some limitations related to ARM architecture, for example, the runner cannot run on a host with ARM architecture. However, I'm not aware of a limitation about using ARM Docker images as build containers. The error message also doesn't mention anything specific to ARM.

In order to investigate this further, could you please share the following details?

1) Based on your description, I assume that you are using Linux Docker Runners, and these images you mention (alpine, ubuntu, arm64v8/ubuntu) are specified as build containers in your bitbucket-pipelines.yml file. Is that correct?

2) What version of the runner are you using?

3) Is the machine where you have set up the runner in one of our supported platforms mentioned below?

• https://support.atlassian.com/bitbucket-cloud/docs/runners/

4) Could you please post here:

• the Pipelines build log from a step that fails with this error
• and the Pipelines runner log (just the entries at the time of the failed step)

Please make sure to sanitize any private/sensitive data prior to sharing.

You can download the build log while viewing it on our website, there is an option in the top right corner.

The runner log is located at /tmp/b609961f-891e-c872-c36b-f3f2c315d186/runner.log on your machine, where b609961f-891e-c872-c36b-f3f2c315d186 should be the UUID of your runner.

Please feel free to let me know if you have any questions.

Kind regards,
Theodora