benyanke Posted June 26, 2017 Share Posted June 26, 2017 When I try to forward port 53/tcp and port 53/udp to a container, it triggers the duplicate port protections. Is this a known bug, and is there a workaround? Quote Link to comment
benyanke Posted June 26, 2017 Author Share Posted June 26, 2017 /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint bind (b02afe12d7e2bd9ea08cae7ad3bdeecab9609f8278418a8fb71f9a1ad042c6b1): Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use. Quote Link to comment
Squid Posted June 26, 2017 Share Posted June 26, 2017 Probably because port 53 tcp is already in use to handle DNS requests from the container itself to the host system. Quote Link to comment
bonienl Posted June 26, 2017 Share Posted June 26, 2017 unRAID runs dnsmasq which is already listening/using port 53. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.