-
Notifications
You must be signed in to change notification settings - Fork 292
local dns fails to resolve inside containers in 18.06, fine in 18.03.1 #2301
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
Comments
@pavlovpetr - I'm not sure this is the same issue, I can pull just fine, it's DNS resolution inside containers rather than while trying to pull. Any chance you could open a separate issue for your problem rather than confusing this github issue? |
+1 for this issue. I have same problem with 18.06 while everything works well in 18.03. I'm working behind corporate proxy. |
I think I found a solution. Configure 18.06 docker daemon based on your host machine dns properties or etc/resolv.conf file from any container running with 18.03. For example you may need to add dns-search domains as follows: "dns-search": [ I think new version has an issue to configure its dns properties based on host machine automatically. This solution works for me however there are still some network issues in new version. |
+1. Adding (I am using However, adding the following to the daemon settings (Docker for Windows -> Settings -> Daemon ->Advanced -> Apply) does not work for me. It doesn't seem to add anything to /etc/resolv.conf.
Looking in the logs, I can see there was an ENOENT editing the /etc/resolv/conf file.
I know this was working fine previously, and have upgraded recently. (Not sure of exact versions.) |
This looks related: #2304 |
Yep, let's track on #2304 |
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
Actual behavior
Information
This was working fine in 18.0.3.1, so I've downgraded to that, which is why there's no diagnostics dump.
It looks just like a search domain issue (ie: what ends up in
/etc/resolv.conf
when the container is instantiated...)Steps to reproduce the behavior
docker pull <local image based on RHEL>
docker run -it <local image based on RHEL> bash
ping <corporate ip>
The text was updated successfully, but these errors were encountered: