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
Unable to use Docker when DNSMasq is running #220
Comments
since this has come up a few times, i'm wondering if this is a pattern that's common.. how do you have dnsmasq installed? how is it configured? how do you run it? if there's some common pattern maybe i can somehow inject configuration to work around it, binding dlite's dns resolver to some alternative port and have dnsmasq forward requests for the tld to it. |
I'm on macOS 10.11.5. I installed dnsmasq using Homebrew. I have it configured for multiple purposes:
for 1., it's something like this:
For 2., I'm just importing multiple host files from an external hosted repository ( For the rest, I think my config files are pretty much forward. But, if you are interested, I could post an extract of my configuration? If that could be helpful. |
do you keep your config file at the standard i'm wondering if rather than creating the |
you might try those steps, actually..
see if everything works after that note: i'm assuming you kept the default vm hostname of local.docker |
Yes and no. The configuration file is in And in my
|
Silly me! I still had my interface restrictions / exclusions in place. Now it seems to boot and work correctly! :) |
darn. so my assumption here is that dnsmasq isn't listening on the bridge interface that the vm is trying to use, can you configure it to listen on 192.168.64.1 in addition to 127.0.0.1 and try again? |
Yeah, you're right ;) My |
should be |
Thanks for your quick response time & solve! Just chiming back in. As you mentioned above, last night, I added sudo rm /etc/resolver/docker
echo "server=/docker/127.0.0.1#1053" >> /usr/local/etc/dnsmasq.conf
sudo brew services restart dnsmasq That did the trick of combining my dnsmasq installation + running docker & dlite in harmony. Great! However, this morning I did a reboot of my computer. And I fell back into the exact same issue... In the meantime, I think this issue can be closed? Maybe add your 'workaround' somewhere in the Some additional debugging infoI don't really know why it started working after dnsmasq restart? Might be a caching issue from my side (
|
Bug Reports
dlite --version
):dlite version 2.0.0-beta9
Be able to pull docker images.
While dnsmasq is active, run
dlite start
.When you execute e.g.
docker pull nginx
, you will get the error message above.I know this issue came up briefly in #135, but that thread was closed...
Is there a known solution for this, so that I can use dnsmasq together with dlite?
Because, dlite seems to work a lot faster (and easier) than most other solutions I already tried on macOS... ;-)
Things I already tried
When I stop dnsmasq and restart dlite, the problem goes away.
Docker starts pulling in the images as it should. Great!
And it seems like it keeps working when I restart dnsmasq, after I started dlite?
Already tried updating my dnsmasq.conf for
en0
(Wi-Fi) anden1
(ethernet)en5
(an interface which only seems to exists when dlite is running)The text was updated successfully, but these errors were encountered: