Unable to pull image: Get \"https://k8s-docker.packages.atlassian.com/v2/\": net/http: TLS handshake

[Alexei.Yugov]

​Hello. I'm experiencing an issue with my Linux/Docker runner. Occasionally, for the same commit, I encounter the error "Unable to pull image: Get \"https://k8s-docker.packages.atlassian.com/v2/\": net/http: TLS handshake timeout", or "Unable to pull image: Head \"https://docker-public.packages.atlassian.com/v2/sox/atlassian/bitbucket-pipelines-dvcs-tools/manifests/prod-stable\": Get \"https://docker-public.packages.atlassian.com/api/docker/docker-public/v2/token?scope=repository%3Asox%2Fatlassian%2Fbitbucket-pipelines-dvcs-tools%3Apull&service=docker-public.packages.atlassian.com\": net/http: TLS handshake timeout"
But sometimes a build for the same commit is passed successfully!
The behavior has been observed since January 2023. Is there a way to extend the TLS handshake timeout limit?"

[Syahrul · Accepted solution]

G'daym @Alexei.Yugov 

The issue might be related to your local network rather than the runner. So, merely extending the timeout limit may not offer a permanent solution.

Since this issue is related to your network, I can offer some potential avenues for investigation that might help identify the cause of the error:

• Investigate whether recent modifications to the runner's host setting or network could have triggered this error.
• Examine if Docker is setup to utilize any proxy (Change Docker Desktop settings). Ensure the proxy is functioning correctly.
• If a firewall protects the runner's host, verify that "*.packages.atlassian.com" is not being obstructed by any proxy or firewall within the network.
• Attempt to launch the runner on an alternate machine (where the local pull operates) and determine if the build is successful.
• Consider upgrading Docker to the most recent version if it's outdated.

Let me know how it goes.

Regards,
Syahrul