nginx-proxy / nginx-proxy/nginx-proxy
routing issues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
I have a few issues where I need to route back out to the proxy from one docker image to another that are hosted on the same server/network. Is it possible to have it route properly (hit the proxy first and go in that way, instead of going from docker container to docker container)?
I have something like
gitlab.mynetwork.com
sonarqube.mynetwork.com
jenkins.mynetwork.com
For example, jenkins is setup to call sonarqube during a job. Right now I have to call it by the container name I give it to get the 17.0.0.0/16 network. I would like to route it so it hits the proxy and then routes from there. Is this possible?
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
The issue names Docker containers and an nginx proxy but provides no repository file, test, or entry point. Start by checking whether a request from Jenkins to SonarQube can traverse the proxy rather than the container network; done means the documented hostnames route through the proxy successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100