Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,560,577
Community Members
 
Community Events
185
Community Groups

Bitbucket Self hosted runner failing

Adrian Chung
Adrian Chung Jun 21, 2022
Runner matching labels:
- linux
- self.hosted
Runner name: Runner1
Runner labels: self.hosted, linux
Runner version:
current: 1.330
latest: 1.330

Status 404: {"message":"pull access denied for sox/atlassian/pipelines-auth-proxy, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"}

 

The runner is online but when we kick off the runner task the above 404 occurs 

Answer
Watch
Like Be the first to like this
95 views

1 answer

0 votes
Patrik S
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 23, 2022

Hello @Adrian Chung ,

Welcome to Atlassian Community!

From your description and the error you have shared, it seems like you might have been affected by the following incident :

A fix for that incident was already deployed, so could you please try running your pipeline again and let us know if you are still facing the same error? 

Thank you, @Adrian Chung .

Kind regards,

Patrik S

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

See all events