sameersbn / sameersbn/docker-gitlab
Cannot be accessed by domain name after Upgrade 17.9.1
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
When docker is deployed containerized, the configuration file is not modified except for the container version. However, after the upgrade, the configuration file cannot be accessed through the domain name, and IP access is not a problem. Domain name resolution has been confirmed.
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 Dockerized GitLab deployment after upgrading to 17.9.1, comparing access through the domain name with direct IP access. Review the container configuration and domain-resolution path described in the report. Done means the upgraded deployment is reachable through its domain name without breaking IP access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, shell
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100