libp2p / libp2p/go-libp2p-pubsub
pubsub peer discovery when running docker containers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
I followed the pubsub example that uses the mdns peer discovery. This all works perfectly when running my go code in different terminal windows.
I'm a bit confused as to if this approach would work when I go to deploy my code within multiple docker containers. For example, if I had one container publishing messages and then say 5 containers subscribed to those messages. I'm assuming mdns isn't appropriate for this, will I have to use some other form of peer discovery?
Any advice would be greatly appreciated or if there's an example that would be great!
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 with the pubsub example using mDNS peer discovery and review the assumptions that work across separate terminal windows. Determine whether that discovery approach works for multiple Docker containers, then document the supported approach or provide a container-focused example showing how peer discovery should be configured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, distributed-systems, networking
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100