self-hosted running failing on launch

[chus alvarez]

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

[Ben]

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)