-
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
OSX DNS ignored for login
#16230
Comments
@ashley-cui PTAL |
A friendly reminder that this issue had no activity for 30 days. |
Bump issue due to lqck of response. |
Looks like a regression in our Makefile, where CGO isn't enabled for Darwin builds. I'm on it! Thanks for the bump @andrunah, sorry for the late response :) |
A friendly reminder that this issue had no activity for 30 days. |
Still being worked on in PR. |
A friendly reminder that this issue had no activity for 30 days. |
I am imaginging this is fixed, so closing, Reopen if I am misaken. |
@rhatdan linked MR is not merged, how did you decided it's fixed? |
Over zealus I guess. |
@ashley-cui Any update on the PR. |
Spent a day trying to get it through our CI, but it works on my machine and not in CI. I think it might be best to just fix this in homebrew packaging at this point, let me see if I can do it there this week and get this closed out. |
Please correct me if I'm wrong, but this seems to be fixed with golang/go#12524 |
yes, but the fix requires go1.20, which we are not yet on |
The homebrew bottles are built with go 1.20.x.
Thought his info might be helpful for someone else. |
My apologies, you are correct! Closing, thanks! |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
I am trying to log into a container registry, where its DNS name is not resolvable using the resolvers listed in /etc/resolv.conf. However OSX has no problem connecting to it by name.
This appears to be a reincarnation of bug: #12975
podman login works inside the podman machine
Steps to reproduce the issue:
Have a (gitlab) container registry that is not resolvable using the nameservers in /etc/resolv.conf
podman login gitlab-registry.example.org
Observe podman-remote talking to the nameserver in /etc/resolv.conf, and then reporting "no such host" in the debug logs.
Describe the results you received:
Describe the results you expected:
I would expect login to find the registry. I managed to login using v 4.1.1 version, but latest versions (4.2.1 and 4.3.0) seem to have this issue.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
orbrew info podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: