Error updating changes detected dubious ownership

Recently while I mounted a HDD in my Linux workstation, I tried to download a new repo in the new disk so when I executed the command git submodule update –init –recursive, it showed me an unexpected error; ‘fatal: detected dubious ownership in repository at’. A snippet of the error is given below:

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

I would like to share the steps that helped me to fix the ‘fatal: detected dubious ownership in repository at’ error.

The ‘fatal: detected dubious ownership in repository at’ error; is seen because you do not have the proper permissions in your project directory. You have to either ensure that all repositories are to be owned by the correct owner-ID  or bypass the security completely.

To completely bypass the security, add * as a “safe” directory.

A simple and optimal solution to this problem is to, try chown -R <current_user> <repo_folder> this will change the owner and for the directory.

A detailed solution to fix ‘fatal: detected dubious ownership in repository is mentioned below:

How to fix ‘fatal: detected dubious ownership in repository at’ error?

To fix the ‘fatal: detected dubious ownership in repository at’ error, Change the ownership of the directory. This will fix the error and “fatal: detected dubious ownership in repository at’ error will be resolved.

Alternatively disable the Safe Directory manually using the command git config –global –add safe.directory ‘* and it would disable directory config and change the directory setting as [safe] directory = *.

Below are the all possible methods to fix the fatal: detected dubious ownership in repository at’ error:

Method 1: Change Directory Ownership

You can change the ownership manually by following the command chown -R <current_user> <repo_folder>.

chown -R <current_user> <repo_folder>

Following the above mentioned step should fix the error fatal: detected dubious ownership in repository at’ error.

Method 2: Disable Safe Directory Manually

Alternatively to fix the fatal: detected dubious ownership in repository at’ error, disable the Safe Directory Manually, this would remove the all unsafe repository related errors for you immediately.

Disable the Safe Directory, using the command “git config –global –add safe.directory ‘*’”, :

git config --global --add safe.directory '*'

That would change the directory configuration as [safe] directory = * and this would solve the fatal: detected dubious ownership in repository at’ error.

[safe]
    directory = *

if git config –global –add safe.directory ‘*’ command doesn’t work for you and throws error, try to use the command ^{git config --global --add safe.directory "*"} into your terminal. so just changing the single quote with double quote in command git config –global –add safe.directory ‘*’ would help you to run the command without any error.

Note: before using the second method as a fix, you should understand the consequences as well of disabling the safe directory setting. you must avoid to disable the safe directory if your repositories are stored on a shared drive.

Disabling the Safe Directory Manually method can be used if repositories are stored locally on your pc and no unauthorised access can be taken.

Conclusion

To fix the ‘fatal: detected dubious ownership in repository at’ error, Change the ownership of the directory by running “chown -R <current_user> <repo_folder>” command. This will fix the error and “fatal: detected dubious ownership in repository at’ error and error will be resolved.

Alternatively, To fix the ‘fatal: detected dubious ownership in repository at’ error, disable the Safe Directory manually using the command git config –global –add safe.directory ‘*. This will fix the error and “fatal: detected dubious ownership in repository at’ error and error will be resolved.

While I am trying to push my commit I am facing some unwanted error and the error is saying that fatal: detected dubious ownership in repository So Here in This article, We will Discuss how I solved this error. And what are the possible causes of this error?

Solution 1: Add Your Directory to safe Directory

You can check Git Post Related safe.directory You are all facing this warning is related to git’s safe.directory system You need to run the following command to solve all unsafe repo’s warning. Jusr tun this following command in your tereminal.

git config --global --add safe.directory '*'

If You are still facing any error then You need to put double quotes instead of single quotes Just like this.

git config --global --add safe.directory "*"

And this safe directory command will add a safe directory section in your .gitconfig file. and Now, You will no longer face the above error.

Also, Read

• Failed! Error: SET PASSWORD has no significance for user ‘root’@’localhost’ as the authentication method used doesn’t store authentication data in the MySQL server
• Invalid syntax in configuration ini file.
• A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
• How to fix “zsh: command not found: python” error? (macOS Monterey 12.3, python 3.10, Atom IDE, atom-python-run 0.9.7)

To Solve fatal: detected dubious ownership in repository Error You need to disable checks and it will end all the unsafe repository errors in GitHub. In this article, We are going to learn about How to reproduce this error and we will discuss All Possible Solutions Let’s Get Start With This Article.

Solution 1: add safe directory

To Solve fatal: detected dubious ownership in repository Error You need to disable checks and it will end all the unsafe repository errors. But Before Disabling it Just Read This Why This error is Exist and then You can disable it by running this command in your terminal.

git config --global --add safe.directory '*'

By Running git config –global –add safe.directory ‘*’ command it will add this line in your .gitconfig file.

[safe]
    directory = *

And now, Your error will be solved. Thanks.

Frequently Asked Questions

Conclusion

You need to add a safe directory and it will resolve your error. I hope this article helped you. Comment below on which solution worked for you.

Also, Read

• Creating a personal access token in Github
• Please use a personal access token instead in GitHub
• command github.copilot.generate not found GitHub Copilot