You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm guessing this is due to avahi (or whatever network discovery SoundSync uses) not having the ports it needs exposed. soundsync-docker can see out, but others can't see in to discover it. Assuming avahi is used, a simple -p 5353:5353 isn't a great idea since it'll conflict with the avahi on the host.
The solution I see here is to set up a virtual network adapter with its own IP and MAC addresses via macvlan, this way the container's interface can grab its own IP and run avahi/whatever independently of the host.
The text was updated successfully, but these errors were encountered:
I'm guessing this is due to avahi (or whatever network discovery SoundSync uses) not having the ports it needs exposed. soundsync-docker can see out, but others can't see in to discover it. Assuming avahi is used, a simple
-p 5353:5353
isn't a great idea since it'll conflict with the avahi on the host.The solution I see here is to set up a virtual network adapter with its own IP and MAC addresses via macvlan, this way the container's interface can grab its own IP and run avahi/whatever independently of the host.
The text was updated successfully, but these errors were encountered: