Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Other SoundSync instances can't find soundsync-docker over the network #1

Open
dustin-richards-was-here opened this issue Sep 4, 2022 · 0 comments

Comments

@dustin-richards-was-here
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant