-
Notifications
You must be signed in to change notification settings - Fork 243
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
[BUG] 2.43.0 broke darwin public DNS query when host do not exclusively use IPv4 DNS servers. #4454
Comments
Can you provide more details about the steps you are following to reproduce, and can you share logs of crc startup ? |
FWIW got 2.42.0 working now. |
Here's a fun function I just made..
|
@cfergeau I got cluster to come up but the issue with curl for dns remains. AND is specific to 2.43.0
|
can you follow the steps here https://github.com/crc-org/crc/wiki/Debugging-guide#entering-the-vm to check network connectivity inside the VM? |
Not yet successful with that guide
|
|
|
from the vm can't curl quay.io
|
|
no hostnames works afaict |
Upon further inspection.. no 4.17.1 without DNS is not running fine. A bunch of system operators are failing to lookup.
|
im back to 2.42.0 until further instructions. |
dotfiles for more info |
on the macos machine zsh terminal
|
For the record, on the host system quay works.
|
Could be containers/gvisor-tap-vsock#398 |
2.42.0 worked fine so I guess they technically regressed that repo |
@kaovilai could you try to swap the 2 entries in /etc/resolv.conf and re run crc delete/crc start? |
For the record I never went or edited this file manually. Everything was done through system preferences. I will report back after reordering. Will check if the order is same in system preferences first and see if reordering there first works. |
With
I am still getting
|
I will stop troubleshooting now by removing ipv6 dns from this adapter for the time being. |
This is fixed with containers/gvisor-tap-vsock#426 PR |
@evidolob which CRC version will have fix? |
Opened #4496 |
General information
crc setup
before starting it (Yes/No)?CRC version
# Put `crc version` output here 2.43.0
CRC status
❯ crc status --log-level debug DEBU CRC version: 2.43.0+268795 DEBU OpenShift version: 4.17.1 DEBU MicroShift version: 4.17.1 DEBU Running 'crc status' CRC VM: Running OpenShift: Running (v4.17.1) RAM Usage: 5.973GB of 10.93GB Disk Usage: 18.97GB of 53.08GB (Inside the CRC VM) Cache Usage: 116.6GB Cache Directory: /Users/tiger/.crc/cache
CRC config
Host Operating System
Steps to reproduce
Expected
Actual
Logs
Before gather the logs try following if that fix your issue
Please consider posting the output of
crc start --log-level debug
on http://gist.github.com/ and post the link in the issue.https://gist.github.com/kaovilai/44f9f77e00455d76283542eddd9d59c7#file-2-43-0-curl-error-log-L288
After some tinkering I think I got cluster up.
v2.42.0...v2.43.0
The text was updated successfully, but these errors were encountered: