sameersbn / sameersbn/docker-gitlab
can't push repo via SSH
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
my company installed GitLab enviroment on Docker
but someone find out they can't push their repo via SSH
nothing wrong with ssh-pub-key, I already checked!
when they enter
git push -u origin master
required to enter
gitlab@192.168.1.xxx's password:
HTTPS works well
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing git push -u origin master against the Dockerized GitLab environment and compare the SSH remote with the working HTTPS remote. Trace the container's SSH endpoint and GitLab SSH configuration to determine why the connection requests the gitlab user's password; done means repository pushes work over SSH using the configured public key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, gitlab
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100