L4T arm64 self hosted build runner error

[이제혁]

I am running bitbucket build runner on a jetson Orin machine.

Since updating the runner some time ago,
I'm getting the following error.

Unable to run script in container 02ce19b0-d3e2-5dce-af36-42b1cbba2345_94d92430-6933-4092-bb65-9f9ad3a7c47d_clone. Container exited prematurely with code 1.

After investigating in several directions,
I noticed that the bitbucket-pipeline-docker-daemon image was versioned up.
And BUILDKIT became the default, which made the privilege option mandatory.
When running docker-daemon from bitbucket runner, I can't find a way to run it with privilege. What should I do?

[Theodora Boudale]

Hi @이제혁 and welcome to the community!

Based on the error you provided, it looks like the runner is having issues while it's trying to clone the repo.

Could you please provide the following info so I can better help you?

1. If you open the failed build from the Pipelines page of the repo and expand the section Runner in the build log of the failed step, are there any errors listed there?
   
   
2. Could you please provide the entries from the runner log at the time of the failed build? You can find the build log at the following location on the runner's host machine:
   

   /tmp/b609961f-891e-c872-c36b-f3f2c315d186/runner.log

   
   where b609961f-891e-c872-c36b-f3f2c315d186 should be the UUID of your runner.
   
   Please sanitize private/sensitive data from the log, if any, before sharing.
   
   
3. Is your runner running on a supported platform and does the host machine meet the minimum requirements? Supported platforms and minimum requirements are listed on this page:
   
   
   • https://support.atlassian.com/bitbucket-cloud/docs/runners/
     
     
4. Based on the error message, it doesn't look like the issue is related to BUILDKIT. I've seen this error occur when the runner fails to clone the repo at the beginning of a step. BUILDKIT issues with privileged mode may arise when you build a Docker image during your build. Can you please confirm if this error occurs when the runner tries to clone the repo or at a different stage of the build?

Kind regards,
Theodora