Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

self-hosted running failing on launch

chus alvarez
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 11, 2023

After launch again a runner, the docker seems to crass on entry point:

 

+ ./entrypoint.sh

Error: Unable to access jarfile config

 

The image failing is the currently set to "latest" one: 

 

 

    Image:         

docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner:latest

    Image ID:       docker-pullable://docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner@sha256:a06a16bfe447223a7bd965871e3394c32dd70aab34164bbbe8dafc786411c3c1

 

1 answer

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 11, 2023

Hi chus,

Welcome to the Bitbucket Cloud community!

To clarify - if you attempt to re-run the build, does the same crash occur? I am unable to reproduce this behaviour with the same Runner image that you are using on my own repository.

Cheers!

- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events