oyvindo wrote: > I guess I do not know enough about how a docker environment operates > then. When you say "firewall" I guess what you mean is the internal > default gateway in the container (?) > > Code: -------------------- > > Starting Squeeze2cast: /srv/squeezebox/cache/InstalledPlugins/Plugins/CastBridge/Bin/squeeze2cast-x86-64-static -Z -I -f /srv/squeezebox/logs/castbridge.log -d output=debug -x /srv/squeezebox/prefs/castbridge.xml > [22:19:23.815742] main:1186 Starting squeeze2cast version: v0.2.2.1 (May 30 2016 @ 10:17:57) > > [22:19:23.815874] main:1216 Buffer path /tmp > [22:19:23.817192] Initialize:814 UPnP init success - 10.0.3.1:49153 -------------------- > > > The internal network of the container is 10.0.3.x and as can be seen > above the port number castbridge is trying to listen to is 49153 (?) > But how do I "authorise castbridge to open this port" for listening? > If castbridge tries and fails, would there be some error message in > the log?
No, there would not be an error message. The port is opened but nothing is being routed to it from the outside. How to do it really depends on your Linux distribution and how your layers are built. I'm not a docker expert, but I think it's more a Linux problem than a docker one: what's your base image and what mayers have you added. LMS 7.7.5 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos 2xPLAY:1, PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBMC, Foobar2000, XBoxOne, JRiver 21, Chromecast Audio, Chromecast v1, Pi B2, Pi B+, 2xPi A+, Odroid-C1, Cubie2 ------------------------------------------------------------------------ philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=104614 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
