Changing internal container listen port? (adding docker-wyze-bridge to TrueNas) #1415
-
Hi, Im adding docker-wyze-bridge as an app in the TrueNas Scale repository . I tried to change the docker command to "flask run --port 35000" (where 35000 would be user defined in the TrueNas UI), but the UI fails to load. However, inside the container it is not listening on 5000, and responds fine on 35000. outside the container, i get no response on 35000. The port mapping in this case is 35000:35000. if I map the host port 35000 and leave the internal port alone at 5000 (port mapping 35000:5000) the UI loads on 35000. In TrueNAS they prefer to allow the backend port to be changed if possible to help users avoid conflicts. 5000 is unfortunately really common due to flask. Any tips? I havent had a chance to look deep yet. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
i just realized when i added "--port 35000" i had removed "--host 0.0.0.0". Its all working now 🎉 full command
|
Beta Was this translation helpful? Give feedback.
i just realized when i added "--port 35000" i had removed "--host 0.0.0.0". Its all working now 🎉
full command