Pipelines failing: can't pull images

[Caleb Sheirer]

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]: 502 Bad Gateway

my current pipelines jobs are failing consistency with a bad gateway error when i kick things off. looks similar to an outage from back in July.

others experiencing this? maybe another instance of an outage?

[Ben · Accepted solution]

G'day @Caleb Sheirer

I've responded to your reply on another community post but just in case:

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)

[Aliza Naz]

The error message you're encountering indicates that there is an issue with pulling and unpacking a Docker cursed persona 5 images from the specified registry. The error code "502 Bad Gateway" typically suggests a problem with the server or a gateway between the client and server.

Here are a few steps you can take to troubleshoot the issue:

1. **Check Registry Status:** Verify if the Docker registry "docker-public.packages.atlassian.com" is currently experiencing any outages or issues. You can check the status of the registry by visiting its website or checking any status pages they might have.

2. **Network Issues:** A "502 Bad Gateway" error can also be caused by network issues. Ensure that your network connection is stable and that there are no firewall or proxy issues preventing your CI/CD system from accessing the Docker registry.

3. **Retry the Operation:** Temporary issues can sometimes be resolved by retrying the operation. It might be a transient problem that could be resolved with a subsequent attempt.

4. **Check for Updates:** Ensure that you are using the latest version of the Docker client. Updates may include bug fixes and improvements that could address the issue.

5. **Contact Atlassian Support:** If the issue persists and it seems to be related to the Atlassian Docker registry, you may want to reach out to Atlassian support for assistance. They can provide more specific information about the status of their services and help troubleshoot the problem.

It's also worth checking the Atlassian community forums or other relevant forums where users might be discussing similar issues. Others in the community may have encountered and resolved similar problems, and you might find helpful insights or workarounds.