`git pull` fails in pipeline with error `Could not resolve proxy: host.docker.internal`

Christof Koegler _Gaims GmbH_

We use a pipeline step which pushes changes made during that step to the main branch of the repo. This has worked fine over the last couple of months. Today, the pipeline failed when trying to git pull, with the error message:

<span>Could not resolve proxy: host.docker.internal</span>

The pipeline is run by a self-hosted linux docker runner, version 1.413. 

The pipeline step:

 

Pipeline error:

The `hint` is unrelated. 

Pipeline success a few days ago:

 

What could be the issue here?

• Some problem with the runner?
• Some change on the runner host?
• A change in the base image of the step (minor upgrade in python:3.11 image)?
• Something else entirely?

Thanks for your help,

Chris

Theodora Boudale

Hi Chris!

I have been able to reproduce this error, and I think the culprit is that the proxy URL gets changed after the execution of the pipe bitbucket-pipe-release.

I used the command git config --list before and after the pipe's execution:

Before:

http.http://bitbucket.org/my-workspace/my-repo.proxy=http://localhost:29418/

After:

http.http://bitbucket.org/my-workspace/my-repo.proxy=http://host.docker.internal:29418/

I have raised the issue with the development team, I think something might have changed with how pipelines work with Docker containers. Were you also using the pipe before, when the git pull command was successful?

The workaround at the moment is to add a command in the script of your yml file, after the pipe command and before the git pull one, that changes the proxy to what it was. You can use the following command:

- git config http.http://bitbucket.org/${BITBUCKET_WORKSPACE}/${BITBUCKET_REPO_SLUG}.proxy http://localhost:29418/

Please feel free to let me know how it goes and if you need anything further.

Kind regards,
Theodora