sameersbn / sameersbn/docker-gitlab
when i started gitlab the host is not right
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
when i started the gitlab CONTAINER, and created a new project. i found that the address changed ,like this:git@207c7671bc64:root/test.git
207c7671bc64 is gitlab's CONTAINER ID, i use docker like this:
docker run --name gitlab -d --link gitlab-mysql:mysql --link gitlab-redis:redisio --publish 10022:22 --publish 10080:80 --env 'GITLAB_PORT=10080' --env 'GITLAB_SSH_PORT=10022' --env 'GITLAB_HOST=wangchao.life' --env 'GITLAB_TIMEZONE=Beijing' --volume /Users/super/Documents/data/docker/gitlab/gitlab:/home/git/data 989b011ef775
why?
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 the reported docker run invocation with its GITLAB_HOST, GITLAB_PORT, and GITLAB_SSH_PORT environment variables, then inspect how the new project's clone URL is generated. Done means the displayed SSH URL uses the configured host and port rather than the container ID.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, git
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100