April 7, 20197 yr Hi all - I know this has been discussed in a multitude of other threads, but I'm one of the people that set a custom IP using macvlan and want to use port 80 to make it easier to access a container's web UI and I'm a little confused. I know you can change the Web UI port for a few different services, but what I don't understand is when setting the following in "Extra Parameters" on the container edit page: -p 80:8080 If I have the container IP address set to 10.0.0.5, the web UI port is at 8080, why doesn't http://10.0.0.5 get me to the web UI? Is some macvlan magic taking precedent over the Docker parameters? (Or is there a more obvious way to do this that I'm missing? Specifying ports in the variables doesn't seem to do much in v6.6.7) and obviously thank you devs for this amazing product that I'm too dumb to use Edited April 7, 20197 yr by vanik didn't want that to sound sarcastic
April 7, 20197 yr Because when an app is on its own IP address then port mapping is completely ignored. To change the webUI for the app in such a circumstance you have to tell the app to look at port 80 instead of 8080 usually via a config file in appdata (if it supports such a thing)
April 7, 20197 yr Author Hmm... so all the ports are available? Using Sonarr for an example: if I set the web UI port to "80" instead of "8989" in the app config itself, I still can't seem to connect to http://10.0.0.5
April 8, 20197 yr Author Restarted both the container and Unraid and the new port is still unavailable. I must be missing something...
April 8, 20197 yr Community Expert I think the port you want to use needs to be exposed in the dockerfile (used to build the image) also
April 8, 20197 yr Author Hmm... wouldn't setting a parameter like -p 80:80 accomplish the same thing with the engine?
April 8, 20197 yr 1 hour ago, tjb_altf4 said: I think the port you want to use needs to be exposed in the dockerfile (used to build the image) also Not true.
April 9, 20197 yr 3 hours ago, vanik said: So am I just out of luck then? Seems like there is no way to do this... The reason you can't access it at port 80 is that you need to be root to use that port.. If this is our container, it's running as user abc and do not have privileges to use port 80. Edited April 9, 20197 yr by saarg
April 9, 20197 yr Author Ahh, I see. I assume running a container as root is ill advised from a security perspective?
April 9, 20197 yr 7 minutes ago, vanik said: Ahh, I see. I assume running a container as root is ill advised from a security perspective? That is correct. Why do you need to run it on port 80?
April 9, 20197 yr Author Literally just for URL simplicity. It's easier to tell my wife to go to http://sonar.local than to explain it has to be http://sonar.local:8989
April 9, 20197 yr 2 hours ago, vanik said: Literally just for URL simplicity. It's easier to tell my wife to go to http://sonar.local than to explain it has to be http://sonar.local:8989 Bookmark. WAY easier than typing http://sonar.local I literally can't think of a browser that runs on a current OS that doesn't have bookmark or shortcut functionality.
April 9, 20197 yr Author I still have to give the URL to people for them to bookmark it. The question is if it’s possible to use port 80
April 10, 20197 yr 16 hours ago, vanik said: I still have to give the URL to people for them to bookmark it. The question is if it’s possible to use port 80 You still have to give them the link for them to use it, so what is the difference?
April 10, 20197 yr Just now, vanik said: 17 hours ago, vanik said: The question is if it’s possible to use port 80 That question have been answered.
Archived
This topic is now archived and is closed to further replies.