This repository has been archived by the owner on Feb 1, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Multicast and overlay network #1691
Labels
Comments
Really ?! 😨 Does the doc give details about it? I can't find anything about that. I really did not expect such drawback. Where can I find info about it without getting lost in the source code? |
@auzias Oh this is a bad news for you. But I think multicast will be implemented soon enough or maybe you can try some third-party plugins. |
Any suggestion for third-party plugins? I don't get the link between the moby/libnetwork#522 and mine. |
@auzias Sorry for my typo it's moby/libnetwork#552. |
@mavenugo where should I start to contribute ? |
Closing this issue since it's a |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am testing a application using multicast for the discovery. I created a Swarm cluster and a
network create -d overlay swarm-net
so the containers share the same LAN across the several Swarm agents hosts.The discovery seemed to not be working, so I installed
tshark
.tshark
shows the IP address node within whichtshark
is running and the multicast address for the packet being sent thoughtshark
does not show any incoming multicast packet.Note that, as I don't know a better way to do so, the container is run with
--privileged
to enabletshark
.Is the multicast blocked because of Docker iptable?
How to enable multicast in an overlay network?
Any help would be welcome. I don't know if it is a bug or just an obvious issue I can't debbug myself, this is also post on SO.
Environment details
docker version
docker info
uname -a
docker -H tcp://0.0.0.0:5732 -v #swarm-docker -v
consul -v
The text was updated successfully, but these errors were encountered: