Pipeline fails: failed to resolve reference

René Dyhr July 19, 2024

Getting this issue in Piplelines. Is there a service disruption?

rpc error: code = Unknown desc = failed to pull and unpack image "docker-registry/development:latest": failed to resolve reference "docker-registry/development:latest": failed to do request: Head "https://docker-registry/v2/development/manifests/latest": dial tcp: lookup docker-registry on 10.61.128.2:53: read udp 10.61.215.93:45871->10.61.128.2:53: i/o timeout

 Pulling works fine on own computers. And sometimes the pipeline will go through with some steps and sometimes some other steps. Very random.

* Registry url has been removed to keep privacy on private registry.

1 answer

1 accepted

1 vote
Answer accepted
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 21, 2024

Hi René,

May I know if you are still encountering this issue? As far as I can tell, there was no incidents reported by us on the date you specified.

Cheers!

- Ben (Bitbucket Cloud Support)

 

René Dyhr July 22, 2024

It fixed itself, but we experienced it a lot for half an hour or so around the post time.

Luckily we don't use Pipelines 100% yet, but this kinda shows the issues when something like this happens since we're not able to build anything.

Suggest an answer

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

Atlassian Community Events