Open codyps opened 8 months ago
This appears to no longer be reproducible for me, possibly due to system changes pushed by corporate (iow: DNS now resolves properly inside docker containers running on rancher desktop).
New state of "VPNs & Filters":
A change to enable Microsoft Defender more fully seems to have gone out.
Feel free to close for now if this is not reproducible for others (I expect there's some funky configuration/software that is causing it). I'll report back if it re-occurs.
Let me know if there's any additional info I can capture when the issue occurs (or while it isn't occuring) that would be useful for debugging it.
I'm experiencing the same problem on M1 Macbook Air, macOS Sonoma 14.5. Rancher Desktop version 1.13.1
how can I troubleshoot this?
btw, after running rdctl shell, there's no dig command in the VM. there's nslookup though.
Actual Behavior
Runs something like
dig +short raw.githubusercontent.com +notcp
, it fails with a timeout every other request. This also effects things likecurl
, causing them to fail to resolve 50% of the time. When usingcurl
, I observe every-other request for the same url returning an error.Example curl output on error:
Note: the next execution of the same command succeeded.
dig output:
Overriding the dns server so it isn't the
/etc/resolv.conf
nameserver 192.168.5.3
, but instead something like 8.8.8.8 seems to resolve the issue.I've been testing in a
docker run -it --rm debian:bookworm
docker image, but the same appears to occur in the lima vm directly:After entering the vm with
LIMA_HOME=~/Library/Application\ Support/rancher-desktop/lima limactl shell 0
Steps to Reproduce
curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh
fails half of the time.Result
DNS resolution failures when using the default DNS host around 50% of the time.
Expected Behavior
DNS resolution succeeds
Additional Information
dig
to usetcp
with a+tcp
makes the resolution always succeed.dig
from macos (and other dns resolution) works without issueThis is on a corporate laptop with a bunch of network filtering/vpn items, and it's possible this issue is triggered by one of them.
In MacOS Settings under "Network" -> "VPN & Filters" -> "Filters & Proxies", these items are present:
Disabling the 2 enabled "Cisco Anyconnect Socket Filter" items does not change the behavior observed. The other enabled items are greyed out and can't be disabled.
Entirely possible this is some weird bug in one of these (though macos dns working seems to indicate some interaction of issues)
Rancher Desktop Version
1.12.2
Rancher Desktop K8s Version
1.28.5
Which container engine are you using?
moby (docker cli)
What operating system are you using?
macOS
Operating System / Build Version
14.2.1 (23C71)
What CPU architecture are you using?
arm64 (Apple Silicon)
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
No response