mherger wrote: > > Is local discovery working? Eg. can any Spotify user in your network see > > SB players? I assume you mean, for example, can I see (and play music on) the Boom in my kitchen from the official Spotty App on my phone. Yes, I can do this. mherger wrote: > > > > successfully, I am currently cheating by using the container in > "host" > > networking mode (in other words, it shares the network stack with the > > host, rather than having its own bridged to the host's interface). > This > > How is this cheating? > Perhaps "cheating" is not the best word I could have used...
For reasons of security and scaling (the latter at least is probably not that relevant for most LMS deployments), the accepted "ideal" container configuration is to have it on its own private network and use bridging (so NATting and port forwarding) to connect to the host / LAN. As discussed, Docker's port forwarding fails if it can't get an exclusive binding on the ports in question: only one container can bind to 5353:udp and it will obviously also interfere with any mDNS daemon running on the host. The various daemons involved seem to coexist okay when they are sharing the host stack (although Avahi 'is grumpy about it' (https://linux.die.net/man/5/avahi-daemon.conf); see section on "disallow-other-stacks"). I spent some time with other configurations, such as MACVLAN, which should, theoretically, allow the container to have its own virtual adaptor and presence on the LAN (i.e. another ip address), but that comes with additional complexity, additional problems and I actually couldn't get it to work. I'm happy enough with host networking; the goal probably should be to get it going in bridged mode, but at present I don't think that would be possible. > > > The problem is that Shairport needs to advertise on mDNS. It does > this > > Spotty would try to do so, too. That's actually why I was asking these > questions: I've had a few reports from Spotty users having problems > running it inside docker. > I strongly suspect the networking mode is the culprit in most or all of these reports. Bridge is the default and works for LMS in the general case, if the right ports are forwarded, but if 5353:udp is not forwarded or the host's mDNS daemon prevents forwarding (which in my experience stops the container starting, which is probably better than failing silently), this single feature will obviously fail. ------------------------------------------------------------------------ BobSammers's Profile: http://forums.slimdevices.com/member.php?userid=66026 View this thread: http://forums.slimdevices.com/showthread.php?t=111828 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
