Docker for Mac doesn't work properly with IPv6 networks on MacOS Sierra 10.12.4 #1586
Comments
|
@BrendonW thanks for your report. I'm hoping to have a look at the logs tomorrow. |
|
@BrendonW the diagnostic upload has 2 kinds of DNS logs: high-precision packet traces which only cover the time period from when the VM was last started; and low-precision logs which cover a couple of days. In the high-precision traces I can see the following lookups:
-- these seem to be fine. Looking at the (less accurate) older logs, I see logs like this: -- this might mean you're still suffering from a recent bug where However I also see unrelated errors of the form: -- this suggests that there is some stale authentication information in your If it's still failing, could you do the following:
I'm not sure yet how IPv6 fits into the picture but I've escalated this to our networking team and they're taking a look. |
|
Thanks for the response Dave. I'll work through all your suggestions and let you know the results of each one. I'll also grab my daughter's macbook and install the, theoretically same, combination of OS and EDGE. If that works on this network, then digging into why MY machine has the problem will have a different focus. In the last week, while trying to debug, I see lots of people who seem to have (some) specific similar symptoms and could be suffering from a related issue. Hope I can help make the product more robust, because I'm in love... |
|
|
Morning Dave, After installign the vpnkit, apk update now works inside existing containers even with IPv6 in place. This is what I get whenever I try to pull an image: This is after removing the Auth section from .docker/json.conf I will have to upgrade my daughter's mac -- as soon as I get her AppleID and wait the 50 hours that a Sierra upgrade takes :) and then will see if her machine works here. |
|
@BrendonW good news about the -- the first command runs effectively a root shell inside the helper Linux VM, and the second uses the Linux Another random thought: do you have an HTTP/HTTPS proxy set up? Could that be requiring some authentication? |
|
I upgraded my daughter's Mac and installed Docker for Mac. It worked perfectly on the same network. Now I'm going to try and reinstall on my machine. That's a pain because I believe I have to figure out how (and which images/containers/volumes) to backup so I can put them back after the re-install. |
|
I completely uninstalled Docker and then reinstalled... New Diagnostic ID: 59485F30-B400-41E3-9324-24918BC5FBF5 I'm a bit stumped as to where to go next... but I REALLY need to get docker working again! |
|
Is this a problem? I've seen other reports, but no symptoms, just that the IP doesn't show up in ifconfig. |
|
I tried your experiment on the clean install: I don't have any proxy and have the machine Firewall turned off. |
|
@BrendonW the DNS Sorry, I designed a bad experiment. Could you try this revised version: To exit the screen use 'Control+a' and then 'd'. It's also worth running I checked the IP addresses you're seeing for |
|
I did do a new Interestingly, your So I then tried in a (new) terminal: |
|
@BrendonW that's really interesting -- if the pull succeeds from inside the VM then there must be something wrong with the CLI on the host. Could you check which binary you're running on the host? I have: Could you also check you have no (just in case there's a Another experiment on the host, could you try running -- this bypasses any |
|
From the Terminal:- The CLI binary is in the locations you have. Anything else to try??? |
|
Note, with only one "docker" in the |
|
Could you try: (sorry I had a typo in my original path) -- my guess is that will fail, but just in case. Since it worked on your network on your daughter's computer but not on yours, even after you reinstalled your computer, perhaps there is something specific to your user like a config file or keychain item? Could you try
(Sorry this is taking so long to narrow down) |
|
As you suspected:- I created a new user, non-admin, started docker and ran Here is my env output with the items that are basically the same as the TestUser removed: Hopefully you can see some clues in there... |
|
Current situation after logging out of the test user, and back to my user. This is in the screen tty:- And on the mac terminal: |
|
Thanks for the update -- I can't see anything unexpected in your environment variables. I think the problem must be in the filesystem state. Perhaps try:
(As an aside I'm a bit suspicious that the error has changed from "unauthorized" to "request canceled". I hope the other instance of Docker is definitely completely shutdown -- it might be worth a reboot to make sure) Another possibility:
|
How can I make sure no Docker processes are running? |
|
@BrendonW saw the token -- should have suggested you redact it :) To check if all the docker processes are gone: -- you can kill any process starting with |
|
This is the only thing that keeps running... |
|
|
|
Same results after the clean reinstall -- I didn't bother with the cow backup -- I'd already lost anything I care about in earlier reinstall attempts. I noticed that even though I'd reset everything, I was still logged in... so I logged out and Docker crashed -- or at least went away. I restarted docker and then everything worked! There is some config that is hiding somewhere through uninstalls and reboots... |
|
I did kill vmnet... btw |
|
How can I figure out the problem so we can prevent this happening in the future? |
|
What I don't understand is that I logged/out and in multiple times during the process, and only this last logout "fixed" the issue. This logout was different, because Docker literally vanished when I logged out. |
|
I don't understand the cause yet either :( Let me know if you spot any other recurrences. BTW a new version of |
|
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Expected behavior
I expect Docker to resolve external names to IP addresses correctly
Actual behavior
The problem seems shows itself in many forms, The first was failing "apk update" inside Alpine images.
Another example, which the activity on the host shows it fails to use the correct DNS resolution, leading to a failure:
Information
This seems to be an interaction of the Mac DHCP/DNS resolution system on machines with IPv6 access. Disabling IPv6 on the machine and changing networking settings to use just 8.8.8.8 for DNS allows existing containers to operate correctly (although now your machine can't do IPv6!) internally, but the Docker for Mac VM doesn't stop trying to resolve using AAAA resolvers. And if the destination has no IPv6 address, then even finding a valid IPv4 address, doesn't work because it DOES NOT USE the IPv4 address!
Network settings after trying to workaround by disabling IPv6:
https://www.dropbox.com/s/r84w5w6kg4evykb/Screenshot%202017-05-03%2011.18.39.png?dl=0
and DNS settings
https://www.dropbox.com/s/rtyls95vb1vbn14/Screenshot%202017-05-03%2011.22.38.png?dl=0
A reproducible case if this is a bug, Dockerfiles FTW
Nothing special required.
syslog -k Sender Dockeroutput from a docker restart:-Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: