I am using runner Autoscaler .I have a pipeline stuck on `Pulling Images` for the last 50 minutes.

[sibani.das]

I am using runner Autoscaler .I have a pipeline stuck on `Pulling Images` for the last 50 minutes.

Its happening multiple times and there are no logs

[Theodora Boudale]

Hi @sibani.das and welcome to the community!

• Does this issue occur consistently with all Pipelines builds or only with some of them?
  
  
• If the server where the runners are running is behind a firewall, have you whitelisted the IP addresses needed for runners to run?
  • https://support.atlassian.com/bitbucket-cloud/docs/ip-addresses-for-runners-behind-corporate-firewalls/
    
    
• We would also need to see some logs to better understand what is happening. Could you please get the pod logs when there is a stuck build with the following commands:
  

  kubectl logs pods <pod-name> > runner.log
  
  kubectl describe pods <pod-name> > runner-describe.txt

  
  and then post the content of these two files here? Please make sure you sanitize any private/sensitive data (including UUIDs) in the logs before sharing.

Since you have access to a workspace on a paid billing plan, you can also create a ticket with the support team and share the logs in the ticket instead of posting them here publicly. The support ticket will be visible only to you and Atlassian staff.

You can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation.

Kind regards,
Theodora

[sibani.das]

Upgrading the image helped also tuning resources .

Instead of docker repo now I hosted image on ecr.

Thanks @Theodora Boudale for suggestion

[Theodora Boudale]

Thank you for the update, it's good to hear that the issue is resolved.