Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

new runner doesnt want to start

Nieznaj_ Piotr
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!
Apr 04, 2023

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:

[bb-runner-j4b5t][runner] + ./
[bb-runner-j4b5t][runner] Error: Unable to access jarfile �d?�y
A corrupt file has been uploaded ? 
This is the image iam getting:


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

1 answer

0 votes
Riley Venable (Atlas Bench)
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

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
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!
Apr 06, 2023

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!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events