want access from another port at client host but '-p custom-port:8080' not work, it always litening on 8080 and tips to access from '0.0.0.0:8080'

[hkdeman]

Hello hello! When using docker-compose you should be able to change the listening port in the client by setting "-p 8081:8080".

For example:

You can further alter the port by using "PORT" environment variable

For example:

You should be able to access at 0.0.0.0:8080 in both the cases.

Hope this helps!

[langlichong]

Thank you @hkdeman !
i tried , the container start with another port but 8080, and can not access the app from the tips

my docker container is at a ubuntu server host with inner ip 192.168.54.9 , and after mapping the prot to non-default 8080 , the containner successful, but when i access from my work desktop with http://192.168.54.9:9977 , there is no response :

my netwrok is ok , and other apps deployed can be access successfully !

[hkdeman]

The team just tried to replicate this but was unsuccessful. WhoDB server seems to be accessible throughout the local network (same WiFi connection). Happy to get on a call and try finding the issue - https://calendly.com/clidey/whodb.

This gives us a good idea to create a community channel to chat around this. Will also try setting one :)