Replies: 6 comments 4 replies
-
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. |
Beta Was this translation helpful? Give feedback.
-
Maybe we could add an optional variable like |
Beta Was this translation helpful? Give feedback.
-
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: Making this change also appears to fix things correctly, at least for wallpaper images (I haven't tested sounds) |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
I have similar request when I'm trying to use ipv6 address with the container. |
Beta Was this translation helpful? Give feedback.
-
Is |
Beta Was this translation helpful? Give feedback.
-
I just converted to a Docker install of 8.3.1 and have noticed at least one place where the browser is being passed a URL using the internal ip address of the Docker container (which of course fails). I noticed this in the "Customize Device" plugin, where I believe Slim::Plugin::JiveExtras::Settings is calling Slim::Utils::Network::serverURL() to construct the URLs for the image thumbnails, and this is ultimately using hostAddr() resulting in the internal ip address being used.
I can see that Slim/Utils/Network.pm recently (2021) added an --advertiseaddr parameter, which might have been to address this kind of issue. Would it be useful to formally support and document this as a parameter in the Dockerfile? Happy to try and create a PR if this makes sense.
Beta Was this translation helpful? Give feedback.
All reactions