nginx-proxy / nginx-proxy/docker-gen
A function which limits containers to only those to which docker-gen has access to
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.6k
- Forks
- 609
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 4
Description
If I am running docker-gen inside a container it would be great to be able limit processing of containers only to those docker-gen container can access (to containers in networks in which docker-gen container is by itself). Because docker-gen container can be dynamically added and removed from networks this function should be reactive and trigger regeneration of the output (it is not a pure function).
See #149 for some background discussion.
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 tracing how docker-gen discovers containers, observes Docker network changes, and triggers output regeneration. Define how access is determined for containers sharing networks with the docker-gen container, then verify that adding or removing a network causes the generated output to update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100