Hi James and any others that are having trouble with the Triode Spotify Plugin within the docker container,
I have been battling this issue for about a month now and finally spent the day trying to get to the root.
If you change the network mode of the docker container to 'host' you will notice that the spotify plugin works great. This confirmed that it was definitely a networking issue. I realized that the whole plugin test was actually streaming from the remote player, it dawned on me that the player needs to stream from the LMS, duh. You can see from the Information tab of LMS that the internal IP is NOT the same as the unraid host. So, with docker bridge mode, it is NAT'ing into the container, and the ports you indicated as forwarding are indeed required, however, the IP that the spotify plugin is "announcing" to the client player is the internal IP which it cannot resolve.
So that was the long answer.
There is currently no way to configure the 'external IP' of the docker container to the player. The solution was to jump into the code and hard code the external IP. I found an example of this issue at http://forums.slimdevices.com/showthread.php?79706-Announce-Spotify-Premium-Plugin-%28Beta%29/page140
There were two files that I modified.
/mnt/user/appdata/LogitechMediaServer/cache/InstalledPlugins/Plugins/Spotify/Spotifyd.pm
/mnt/user/appdata/LogitechMediaServer/cache/InstalledPlugins/Plugins/Spotify/ProtocolHandler.pm
I changed the following lines:
from:
my $host = Slim::Utils::Network::serverAddr();
to:
my $host = "x.x.x.x";
where x.x.x.x is my unraid server ip routable from the player.
Hope this helps!
Jeff
Edit: I forgot to mention that the default port for the plugin is 9005. Within the docker configuration, I forwarded both TCP and UDP on port 9005.
