Should Dockerfile support passing in external ip using --advertiseaddr? about slimserver-platforms HOT 5 CLOSED

Just verified that modifying the start-container script to include an --advertiseaddr parameter for slimserver.pl does correct this issue - the "Customize Device" settings page no longer tries to connect to 172.17.0.x, and the image thumbnails are now shown.

I just lazily hard-coded the advertiseaddr ip address for this test but will think about the correct fix.

from slimserver-platforms.

Maybe we could add an optional variable like $EXTRA_ARGS to the startup script (see https://github.com/Logitech/slimserver-platforms/blob/d8120b35f0e8f3991968ab6db1abf22da89ad18f/Docker/start-container.sh#L20). It would be empty by default, but could be set in the Docker command line?

from slimserver-platforms.

I like this idea better than having code specific to --advertiseaddr - makes much more sense.

I do wonder if this has been the wrong approach to my original problem:

JiveExtras::Settings.pm is generating absolute URIs for the thumbnail images. The above fix does make these use the correct (external) ip address rather than the internal docker one. However perhaps it makes more sense just to use a relative URL, like the rest of LMS?

ie, in JiveExtras/Settings.pm (sub _addSettings), change:
my $urlBase = Slim::Utils::Network::serverURL() . "/jive$optname";
to just:
my $urlBase = "/jive$optname";

Making this change also appears to fix things correctly, at least for wallpaper images (I haven't tested sounds)

from slimserver-platforms.

I was wondering about the relative vs. absolute URL. If you're saying it was working with the relative path, then that should be the way to go.

from slimserver-platforms.

I have similar request when I'm trying to use ipv6 address with the container.
Any concern about the extra args? If not I can help to create an PR for it.

from slimserver-platforms.