`git pull` fails in pipeline with error `Could not resolve proxy: host.docker.internal`
Asked by 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:

    Could not resolve proxy: host.docker.internal

The pipeline is run by a self-hosted linux docker runner, version 1.413.  
The pipeline step:  
![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/238623iD9DB020FB8B3A8E1/image-size/large?v=v2&px=999 "image.png")  
Pipeline error:  
![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/238624i8E0E7E2FB4A15929/image-size/large?v=v2&px=999 "image.png")  
The \`hint\` is unrelated.  
Pipeline success a few days ago:  
![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/238627i473BB32EBF34BF26/image-size/large?v=v2&px=999 "image.png")  
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


Answers:
author: Theodora Boudale
body: 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

comments: author: Christof Koegler _Gaims GmbH_
body: Hi Theodora,

Thanks for taking the time to look into this and identifying the problem.
> Were you also using the pipe before, when the git pull command was successful?

Yes, the pipeline itself did not change at all.
> Please feel free to let me know how it goes and if you need anything further.

The pipeline is not critical, so I will wait until your colleagues had a chance to investigate.

One other issue that has probably been resolved, but might be good for you to know:

I had some trouble posting this question and getting updates on it. For a period of around a week before posting this question, I was unable to submit questions. I kept being redirected back to select my product when I tried to save it. Once I did eventually manage to post this question, it seems I was not added to the list of watchers (I believe posters and commenters are usually auto-added). I only stumbled upon your and [@Syahrul](/t5/user/viewprofilepage/user-id/744536) 's answers by accident, when cleaning up my old tabs. That is why I did not get back to you sooner.

Thanks and best regards,

Chris


author: Syahrul
body: G'day [@Christof Koegler _Gaims GmbH_](/t5/user/viewprofilepage/user-id/5011301)

We wish to continue the investigation further and have raised a support ticket on your behalf.

You can view the ticket from our support portal [here.](https://support.atlassian.com/requests/BBS-198673/)

Cheers,  
Syahrul


Tags: bitbucket-cloud

cloud