Difficulty to associate docker_gwbridge entries and service tasks
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
The docker_gwbridge is the solution for my issues, but, I failed to find any association between the task and the ip. It would be great to have an association as observed in the overlay network
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 file, test, or entry point is named. Begin by comparing how overlay-network task/IP associations are represented with docker_gwbridge entries. Done means defining and implementing a reliable association between service tasks and docker_gwbridge IPs, with tests covering the lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100