-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman DNS does not use macOS DNS #12163
Comments
@zeha #11976 allows podman to access the mDNS resolution of the mac when running on the host. That is, podman-remote honors mDNS. /cc @baude @ashley-cui Is there a reason to not make this change to the homebrew formula? No code change is required in podman |
Yep, that's pretty simple to do, I can do it and test it :) |
I've tried to change my local homebrew formula like this, but it does not help. I guess the VM process actually makes the DNS request?
(Or maybe this homebrew formula change did not work...) |
@zeha when you made the change to your local homebrew, did you use brew install --build-from-source? |
Yes!
|
I think you have to use the podman main branch and not 3.4.1 to make sure #11976 is used. |
/kind bug
(could also be a feature I guess.)
Description
Steps to reproduce the issue:
Be on macOS 12.0.1, have a VPN solution (here: Cisco AnyConnect), and a Container Registry (here: GitLab) on an internal network. The registry name is not resolvable without the VPN.
Have podman machine setup normally, i.e.
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Note that
2a02:1748:fad4:5021::1
is one of the IP addresses of my LAN router. Popular VPN clients do not actually rewrite /etc/resolv.conf, especially if the VPN does not capture all the traffic.Output of
podman version
:(No idea why the server is still 3.4.0, I just re-created the
podman machine
.)Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: