git error: detected dubious ownership

[ggwpez]

On Polkadot commit 131fd38b998c861f766909727a600cac201d64d8 with srtool version

{
  "name": "srtool",
  "version": "0.10.0",
  "rustc": "1.69.0",
  "subwasm": "v0.19.1-n/a",
  "tera": "0.2.4",
  "toml": "0.2.4"
}

srtool build -p rococo-runtime --root --profile production on Ubuntu 22.04.2 LTS (user is in group Docker) produces:

    Finished production [optimized] target(s) in 5m 19s                                                                                                        
✨ Your Substrate WASM Runtime is ready! ✨                                                                                                                    
fatal: detected dubious ownership in repository at '/build'                                                                                                    
To add an exception for this directory, call:                                                                                                                  

        git config --global --add safe.directory /build                                                                                                        
fatal: detected dubious ownership in repository at '/build'                                                                                                    
To add an exception for this directory, call:                                                                                                                  

        git config --global --add safe.directory /build                                                                                                        
fatal: detected dubious ownership in repository at '/build'                                                                                                    
To add an exception for this directory, call:                                                                                                                  

        git config --global --add safe.directory /build                                                                                                        
Summary generated with srtool v0.10.0 using the docker image paritytech/srtool:1.69.0

Build is still successful.

[chevdor]

Thanks for the issue @ggwpez. This issue should not(™) happen and was fixed already. I will check again if something changed and triggers this issue again.

Could you please add the output of srtool --version so I test like your system ? (it may be time to add an issue template for that :)).

I think nonetheless that the issue is inside the image.

[ggwpez]

$ srtool --version
srtool-cli 0.11.0

[wischli]

We are experiencing the same issue using the latest image paritytech/srtool:1.73.0-0.12.0. Any update @chevdor?