Port 53 already in use (Ubuntu 16.04.1 LTS) about docker-dnsmasq

[jwulf]

Have a look here:
http://askubuntu.com/questions/500162/how-do-i-restart-dnsmasq

[Caroga]

Thank you @jwulf but I don't see how this applies to my issue?
I'm not looking for (re)starting/stopping the service, I am looking for a way to make them work together.
As I do not know what the consequences are of disabling this service on my laptop I really don't think it's okay just to deactive it.

[andyshinn]

Do you need the dnsmasq container running to server 127.0.1.1:53? It looks like the default Ubuntu dnsmasq is bound specifically to the loopback interface. Could you do something like specify the specific IP address of the host for the container to listen on (such as -p <ip>:53/tcp -p <ip>:53/udp)?

[Caroga]

yeah that might work pretty well, make the dnsmasq server listen on 172.17.0.1.
Ill try that later on, will report back if it works.

[Caroga]

So I've tried the following inside my docker-compose file:

  dns:
    image: andyshinn/dnsmasq:2.76
    cap_drop:
      - NET_ADMIN
    ports:
      - 172.17.0.1:53:53/tcp
      - 172.17.0.1:53:53/udp

But the docker container just exits immediately. I have not found out why.

Edit: same goes for 127.0.0.1

[andyshinn]

OK, that is separate from the port in use issue. That could be related to http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2014q2/008540.html. You need NET_ADMIN to do DHCP stuff with dnsmasq and may also need the dhcp-broadcast option.

[andyshinn]

Going to close this as the original issue didn't seem like it was part of this image but a port clashing issue. Let me know if there is still a problem being experienced.