nginx-proxy / nginx-proxy/nginx-proxy
Failed communicate using VIRTUAL HOST after docker update
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
I have two services, the sevice A inside network A_PROXY, and service B inside network B_PROXY, and have a nginx-proxy using network A_PROXY and B_PROXY.
In this scenario, I have successfully called the domain b.dot (configured in VIRTUAL_HOST inside service B) in docker version 18.06.1 but using version 18.09.2 i receive a error Cloud can not resolve b.dot
Conclusion this problem occurred after update docker
How can resolve this problem?
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by reproducing the two-service setup with networks A_PROXY and B_PROXY, nginx-proxy, and VIRTUAL_HOST=b.dot while comparing Docker 18.06.1 with 18.09.2; done means identifying why b.dot no longer resolves and documenting or fixing the compatible configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100