So I wanted to install linuxserver/smokeping in Unraid Docker. But it turns out that there is no way to change the host port using the Unraid Docker template. And it's default setting is almost 100% sure to collide with another app.

 

Instead I have to do a fully manuall installation direct from the repo. Unless I'm missing something very basic here this means that the inclusion of the image in the Apps directory is useless and a source of yet more beginners frustration. Thus amplifying the feeling that Unraid is not for everyone.

 

So two questions;

 

1. What is the logic behind including a container image that you know won't work for a majority of users?

2. How can there be no host port setting in the Unraid Docker template? Not even in advanced mode.

 

Thank you.

44 minutes ago, Arneby said:

 

 

1. What is the logic behind including a container image that you know won't work for a majority of users?

2. How can there be no host port setting in the Unraid Docker template? Not even in advanced mode.

 

 

It does, if you keep it running on a bridge. (which by default, it ships with)

if you change the network mode to host. That always involves a lot "work". Depending on how the docker container is build, you *could* have it as simple as declaring the port that runs on via a variable or over the config file, if it doesnt, you need to build the docker image yourself to make it work with your usecase.


Edit:

Given that the default ships with bidge as network and port 80, which is used by unraid, its as simple as this.
 

 

 

 

Edited March 1, 20251 yr by Mainfrezzer

I see. Its that first warning dialog at install that throws me of the course. I take warning dialogs to seriously obviously