new runner doesnt want to start

[Nieznaj, Piotr]

Hello y'all,

Iam running a bitbucket runner in a kubernetes cluster.

It has been working fine until I needed to re-apply the job today.

When starting it up, I get this error:

A�=�

[bb-runner-j4b5t][runner] + ./entrypoint.sh

[bb-runner-j4b5t][runner] Error: Unable to access jarfile �d?�y

A corrupt file has been uploaded ? 

This is the image iam getting: 

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

Appreciate all and any help, cause now it refuses to start and our builds are standing still.

[Mike Clarke]

I'm experiencing this problem right now. But instead my error message look like this: 'Unable to access jarfile OaUtHCliEnTiD'. I have tried the steps Riley suggested multiple times and even tried to create a completely new runner multiple times. Anyone an idea?

[Riley Venable]

Based on the error message you received, it seems like the jarfile has been corrupted. You may want to try removing and re-deploying the Kubernetes object spec for the Bitbucket Pipelines Docker-based Linux Runner in your cluster. Here are the steps you can follow:

1. Use `kubectl delete` command to delete the current deployment of the runner in your cluster.

2. Confirm that the runner has been deleted by running `kubectl get` command.

3. Reapply the job by running the Kubernetes object spec file that you used before.

4. Check the logs to confirm that the runner has started successfully. If the issue persists, you may want to consider using a different image for the runner or contacting Atlassian support for further assistance.

[Nieznaj, Piotr]

Yeah, tried that without any luck.

I ended up setting up a whole new runner in bitbucket and configuring my job according to that. It worked. 

Thanks for your reply!

[Siva Abbannagari]

Did you figured this out i get exactly same error?