The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to pull bitbucket-pipelines-runner image

Dennis Lall
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!
November 11, 2024

Hello,

My self-hosted runner is unable to pull the latest bitbucket-pipelines-runner image.

The error I'm getting is:

Error response from daemon: Get "https://docker-public.packages.atlassian.com/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

However, trying this locally (and not on the server running the pipelines) it appears fine.

Is this a case of an IP Block?

Thanks for any assistance,

Dennis

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 12, 2024

Hi Dennis and welcome to the community!

The error could be caused by a slow or unstable network connection, or, it could be a firewall/proxy that is blocking the request and resulting in a timeout error.


If your server is behind a firewall, please check this page:

You will need to allowlist:

  • The IP ranges from the section "Valid IP addresses for bitbucket.org, api.bitbucket.org, and altssh.bitbucket.org" on the above page (except the deprecated ones)

  • The domains listed in the section "Domains for Atlassian public Docker images" on the above page

  • IP ranges from the following page

    https://ip-ranges.amazonaws.com/ip-ranges.json

    filtering to records where the service equals EC2 or S3, and using the us-east-1 and us-west-2 regions.


If you want to configure the runner to operate behind a proxy, please look at this doc for an example on how to adjust the preconfigured command that starts the runner:

Just make sure you use the image

docker-public.packages.atlassian.com/sox/atlassian/bitbucket-pipelines-runner

without the tag 1, to ensure you pull the latest version.

Kind regards,
Theodora

DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events