Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Bitbucket pipeline error - failed to pull and unpack

Edited

I'm getting the following when attempting to run any Bitbucket pipeline:

rpc error: code = Unknown desc = failed to pull and unpack image "docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-auth-proxy:prod-stable": failed to resolve reference "docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-auth-proxy:prod-stable": pulling from host docker-public.packages.atlassian.com failed with status code [manifests prod-stable]: 504 Gateway Time-out

Judging by old Atlassian Community posts, this is not the first (or second, or third...) time this container repository has gone down.

As of the time of writing, there's nothing on the Bitbucket status page. Can we expect a fix anytime soon?

1 answer

1 accepted

1 vote
Answer accepted

Looks like this is an ongoing issue today.  Atlassian Bitbucket Status

Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 25, 2023

G'day @Andrew Palmowski and @Andrew Hewitson

I hope you are doing well. Thank you for reporting the issue to us! Our development team is already aware about the issue.

We had an issue impacting our pipeline service. The issue has been resolved by our team and we apologise for any inconvenience this has caused you. Please re-run your entire pipeline (not just the failed step) as it should be successful now and let us know if you have any issues re-running the pipelines.

Do let us know in case of any further questions!

Cheers!

- Ben (Bitbucket Cloud Support)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events