Unable to access 'git/attributes'

Question

What does warning remote: warning: unable to access \'/root/.config/git/attributes\': Permission denied means and what implications does it bring?

Answer 1

Git is trying to read config from root instead of user config. Please check your environment variables have the correct git config set or the .gitconfig file in your home folder is accessible.

Answer 2

I've ran the similar issue and was able to fix it on server side. git runs there under uwsgi so I added in uwsgi config the following line:

env = HOME=/srv/git

where /srv/git is owned by the same uid that uwsgi runs under and made chmod u+rwX /srv/git So, you need to point HOME variable on server side for the process that runs git to the directory where this process will have reading/writing/traverse permissions.

Answer 3

I think your HOME envireonment variable is improperly set.

From the google group thread,

the HOME environment variable was set to /root so it looked at /root/.gitconfig or /root/.config/git/config since the unprivileged user didn't have access to /root it threw an error.

So the solution was for me to set the HOME env to the user's HOME directory

Answer 4

Go to root directory

cd ~/

Write the following code:

sudo chown -R username /Users/username

Where username is your system's username.

Answer 5

I ran into this situation myself. After verifying that it was looking in ~/.config/ I noticed the owner of that folder was root. I changed this to my_user_name and it worked.

cd ~/
ls -al
<Noticed .config was owned by root, unlike everything else in $HOME>
sudo chown -R $(whoami) .config

It helps to know the cause as well: This directory is created the first time you run a program that uses it. If the command was run as root, it will cause this permissions problem.

For example, if the ~/.config directory does not yet exist, and you run sudo htop, the directories ~/.config and ~/.config/htop will be created and owned by root. Afterward, a regular git command wont be able to access ~/.config and will give the above warning. (Credit: user mehtunguh)

The -R option with chown is to modify the permissions recursively. This will help if you have subfolders under ~/.config

Answer 6

For Windows, it may be a case when some process like CMD or SSH client opened some folder which Git tries to delete.