-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflicts with systemd-resolved #21
Comments
I guess you'd have to heed the advice of the Stack Overflow article and disable Is there something you are proposing we change in this image or documentation to help with this? |
There still exists an issue after disabling Is the container missing a config like |
For starts, how are you running the container and what is the output of |
Okay I think I figured out what was wrong... I was running the container with
And switching to
Now the log seems happy, and
|
It is possible that I'd be happy to accept a README pull request that gives this as an example of how to use the container as a host forwarder. |
Thanks Andy. |
An unfortunate result of using the port mapping instead of
|
Sometimes when the device is restarted the dnsmasq container will be stuck in a reboot loop with the logs showing the following error:
Reason - it's conflicting with systemd-resolved on port 53
see: https://unix.stackexchange.com/questions/304050/how-to-avoid-conflicts-between-dnsmasq-and-systemd-resolved
Host device: Ubuntu 18.04
The text was updated successfully, but these errors were encountered: