sameersbn / sameersbn/docker-gitlab
Cloning via SSH from a group - Project not found
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi,
First, thanks for the great work!
I am trying to clone a repository via ssh but I cannot get it to work... I have already looked at some open/closed issues but none of them solved my problem.
Part of my docker-compose.yml:
gitlab:
expose:
- "443"
ports:
- "8443:22"
nextworks:
- proxy
- default
environment:
- GITLAB_SSH_PORT=8443
The proxy networks is used for the web interface because I am using a reverse proxy in front - It works fine.
I try the following methods to clone:
$ git clone https://gitlab.example.com/group/project.git # Works fine
$ git clone ssh://git@gitlab.example.com:8443/group/project.git
Cloning into 'project'...
GitLab: The project you were looking for could not be found.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
However it works fine for user project...
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 with docker-compose.yml and reproduce the SSH clone using GITLAB_SSH_PORT=8443, comparing the failing group path with the working user project path. Trace the SSH URL and group-project lookup behavior, then verify that cloning the group repository succeeds without changing the working HTTPS path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git, shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100