GitLab requires git@localhost password to push to a repo
I'm trying to get GitLab up and running on my server. I followed the installation instructions at the gitlab github page and everything went well.
The issue is, when I create a repo and try to
sudo git push -u origin master
I am prompted for 'git@localhost's password: '
The git user doesn't have a password, so this is a problem.
Other people who have run into this problem suggested adding git to AllowedUsers in my sshd conf but I don't have an AllowedUsers field in there, so that doesn't seem to be an issue.
I'm still pretty new to ssh stuff so I believe its some sort of ssh key issue, though I tried to add all relevant ssh keys to /home/git/.ssh/authorized_keys and verified that there are no line breaks in the file.
Just FYI, my install completely passes the test provided in the gitlab wiki:
sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production
Any suggestions much appreciated!
EDIT
So, I finally got around this by just committing to a repo from a different machine. As it was, I was SSHed into the same machine that gitlab was running on. As soon as I tried to commit from a machine other than the host, it worked great. So, that may be a solution for some people (it is for us, since we develop on seperate machines than our servers).
This is still an open-ended issue for anyone trying to host and develop on the same machine who has run into this.
Answer
TL;DR
Keys store on both gitlab DB and gitolite side. You should use the factory build gitolite-admin.git folder, don't use your backup! And rebuild the Keys for gitolite later with the update keys command. (update those keys already saved inside the gitlab db to gitolite)
sudo -u gitlab -H bundle exec rake gitlab:gitolite:update_keys RAILS_ENV=production
Most likely it's because there is something issue about the gitolite keys not save properly. Those keys (for login) are actually keep separately by gitlab & gitolite. For pull/push is actually using the keys saved inside gitolite. (git/repositories/gitolite-admin.git/index, git/.gitolite/keydir, git/.ssh/authorized_keys)
gitlab normally should help on saving those imported keys on web to the gitolite files. However, for some reasons it failed. As the keys are not saved properly inside gitolite, the client/server fail to use the keys and fallback to password.
You have to check and fix those keys saved inside gitolite to correct the problems.
check out for more https://groups.google.com/forum/?fromgroups=#!topic/gitlabhq/X0z_9l7L7A8