/etc/resolv.conf in container does not have search domains from host Mac

[keepsimple1]

20180705-142452.tar.gz

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: 75D348B2-67FD-4EDF-A24F-4EC1A6C57D91

Expected behavior

/etc/resolv.conf file in Docker container has the search domain line (e.g. "search <...>") inherited from the host (Mac).

Actual behavior

/etc/resolv.conf file in Docker container has no search domain line.

Information

• macOS Version: 10.13.5

Diagnostic logs

Docker for Mac: version: 18.03.1-ce-mac65 (dd2831d4b7421cf559a0881cc7a5fdebeb8c2b98)
macOS: version 10.13.5 (build: 17F77)
logs: /tmp/75D348B2-67FD-4EDF-A24F-4EC1A6C57D91/20180705-142452.tar.gz
[OK]     vpnkit
[OK]     vmnetd
[OK]     dns
[OK]     driver.amd64-linux
[OK]     virtualization VT-X
[OK]     app
[OK]     moby
[OK]     system
[OK]     moby-syslog
[OK]     kubernetes
[OK]     files
[OK]     env
[OK]     virtualization kern.hv_support
[OK]     osxfs
[OK]     moby-console
[OK]     logs
[OK]     docker-cli
[OK]     disk

Steps to reproduce the behavior

1. Make sure host Mac has "search domains" set in Network Preferences.
2. docker run <...>
3. Check /etc/resolv.conf for the line starting with "search " .

[godbout]

Interested. Having issues with VPN access within containers. Tried to modify resolv.conf from within the container, copy the Mac one through volumes, nothing seems to be working.

[godbout]

Still struggling with this. Any solution?

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[MalikKillian]

Experiencing this issue on Docker 18.06 for Mac. Have confirmed exact same project (build script, Dockerfile, docker-compose) will generate a valid /etc/resolv.conf on Docker 1.12.3 for Mac.

Only workaround is to copy a new resolv.conf into the image and replace it as part of CMD instruction.

[timurkhisamov]

Up, I have same problem on Docker version 19.03.5, build 633a0ea. Any solution updates?

Update: workaround

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

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.
/lifecycle locked