Deploy and build from source code on Bitbucket (git) fails with fatal: detected dubious ownership in repository

Question

Hello,

On some of out App Service servers Git was updated to version 2.39.2.windows.1 which on sync with source code returns error like:

 fatal: detected dubious ownership in repository at 
'//172.17.160.7/volume-12-default/7fdb....
is owned by: 'S-1-5-21-xxx' but the current user is:'S-1-5-82-'
To add an exception for this directory, call:
 git config --global --add safe.directory '%(prefix)///172.17.160.7/volume-12-default/7fdb781'

The problem is that trying to add this exception as suggested returns below error:

error: could not lock config file C:/home/.gitconfig: Permission denied

On servers which still have older git version (2.35.0.windows.1) everything works properly as the ownership check was added in 2.35.2, but likely they will be updated soon.

Is there any other way to get the repository sync working again as we cannot create .gitconfig file or tweak file owners?

Regards,

Rafal

Answer 1

Thank you, worked for me. The only thing I would add that on Azure I was not able to create the file at the c:\home due to permission issues, but I was able to create that file in C:\home\site\wwwroot\my-git-config.txt that set GIT_CONFIG_GLOBAL to C:\home\site\wwwroot\my-git-config.tx

Answer 2

After some tries I come up with workaround that may not be ideal, but works.

In App Service configuration add environment variable GIT_CONFIG_GLOBAL and point it to a text file you created in c:\home. In the file you can add below content:

[safe]
    directory = *

After service restart git will skip the ownership test as it would in version 2.35.0.

Answer 3

Thanks for sharing the solution that worked for you, Orest Khrapko and Rafał Jońca!

Following-up with an update. ( tracking here)

There was a bug identified. The fix has been rolled out by our product engineering team.

Thanks for your patience!