nginx-proxy / nginx-proxy/nginx-proxy
Multiple containers with same VIRTUAL_HOST without load balancing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19.9k
- Forks
- 3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 1
Description
Hi,
I want to know if there is a way to run a new container with a VIRTUAL_HOST already used by another container without load balancing.
I want to keep the older config until the old container isn't stopped.
I want be able to do this in order to have a migration of containers testing the new container before switch the nginx proxy. Now I have the load balancing when I start the new container.
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
Start by reviewing how VIRTUAL_HOST containers are discovered and how the nginx proxy generates upstreams. Determine how an existing container could remain active while a replacement is tested without load balancing, then verify that the old configuration is retained until the old container stops.
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
- 25/100