jpillora / docker-dnsmasq

dnsmasq in a docker container, configurable via a simple web UI
MIT License
734 stars 226 forks source link

(Request) webproc listen port option. #17

Closed tokohito closed 5 years ago

tokohito commented 5 years ago

Hello Dear

My name is tokohito. Thanks your great job!

I also use docker-dnsmasq as DNS and DHCP Server. So I have to set network settings as "host mode".

This is an example of a command that I actually use.

$ sudo docker run --name dnsmasq -d --restart always --network host --privileged -v /var/data/dnsmasq.conf:/etc/dnsmasq.conf --log-opt "max-size=100m" -e "HTTP_USER=admin" -e "HTTP_PASS=password" jpillora/dnsmasq

Unfortunately, the 8080 port that webproc uses by default conflicts with other products. So I want to be change to webproc listen port to any user-specified setting. e.g) -e "HTTP_PORT=5380"

I'm glad if you change the docker image like that.

Best regards!

jpillora commented 5 years ago

You should be able to set the PORT variable

This should be documented, and maybe should be HTTP_PORT instead...

On Sat, 22 Jun 2019 at 8:13 pm tokohito notifications@github.com wrote:

Hello Dear

My name is tokohito. Thanks your great job!

I also use docker-dnsmasq as DNS and DHCP Server. So I have to set network settings as "host mode".

This is an example of a command that I actually use.

$ sudo docker run --name dnsmasq -d --restart always --network host --privileged -v /var/data/dnsmasq.conf:/etc/dnsmasq.conf --log-opt "max-size=100m" -e "HTTP_USER=admin" -e "HTTP_PASS=password" jpillora/dnsmasq

Unfortunately, the 8080 port that webproc uses by default conflicts with other products. So I want to be change to webproc listen port to any user-specified setting. e.g) -e "HTTP_PORT=5380"

I'm glad if you change the docker image like that.

Best regards!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jpillora/docker-dnsmasq/issues/17?email_source=notifications&email_token=AAE2X44ZOVBZ2RQDVZALVOLP3X3OFA5CNFSM4H2WP25KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3CZUWA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE2X46QOBUAB6XEMNSWTRLP3X3OFANCNFSM4H2WP25A .

tokohito commented 5 years ago

Hello Dear.

Thank your reply. I tried to re-run docker by adding the "HTTP_PORT" option. But unfortunately listen on port 8080 instead of the port I specified.

$ sudo docker run --name dnsmasq -d --restart always --network host --privileged -v /var/data/dnsmasq.conf:/etc/dnsmasq.conf --log-opt "max-size=100m" -e "HTTP_USER=admin" -e "HTTP_PASS=password" -e "HTTP_PORT=5380" jpillora/dnsmasq $ sudo lsof -i -P | grep 8080 webproc 11869 root 3u IPv6 1431783 0t0 TCP *:8080 (LISTEN) webproc 11869 root 9u IPv6 1434085 0t0 TCP hostserver:8080->192.168.0.100:57490 (ESTABLISHED)

Could you give me some advice? regards.

jpillora commented 5 years ago

Use PORT

On Mon, 24 Jun 2019 at 12:29 am tokohito notifications@github.com wrote:

Hello Dear.

Thank your reply. I tried to re-run docker by adding the "HTTP_PORT" option. But unfortunately listen on port 8080 instead of the port I specified.

$ sudo docker run --name dnsmasq -d --restart always --network host --privileged -v /var/data/dnsmasq.conf:/etc/dnsmasq.conf --log-opt "max-size=100m" -e "HTTP_USER=admin" -e "HTTP_PASS=password" -e "HTTP_PORT=5380" jpillora/dnsmasq $ sudo lsof -i -P | grep 8080 webproc 11869 root 3u IPv6 1431783 0t0 TCP *:8080 (LISTEN) webproc 11869 root 9u IPv6 1434085 0t0 TCP hostserver:8080-> 192.168.0.100:57490 (ESTABLISHED)

Could you give me some advice? regards.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/jpillora/docker-dnsmasq/issues/17?email_source=notifications&email_token=AAE2X47HGJVARLZMAGLVS3TP36CFPA5CNFSM4H2WP25KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYK7Y6A#issuecomment-504757368, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE2X422IGCJONAOJXOEEH3P36CFPANCNFSM4H2WP25A .

tokohito commented 5 years ago

Oops! Sorry.

Thanks for solving it.

I close this case.