rancher-desktop: DNS resolution inside containers randomly not working
Rancher Desktop Version
1.0.1
Rancher Desktop K8s Version
1.22.6
Which container runtime are you using?
moby (docker cli)
What operating system are you using?
Windows
Operating System / Build Version
Windows 10 Pro 1909
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
No response
Windows User Only
No response
Actual Behavior
DNS resolution inside containers randomly not working. First time it happened a week ago, but after restart it was fine. Then it was fine for few days, but today I can’t get it working even after few restarts.
Steps to Reproduce
> docker run --rm tutum/dnsutils nslookup api.github.com
;; connection timed out; no servers could be reached
Result
connection timed out; no servers could be reached
Expected Behavior
Successful resolution like:
Non-authoritative answer:
Name: api.github.com
Address: 140.82.121.5
Additional Information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 17 (14 by maintainers)
@Nino-K yes, sorry, due to the war in my country I temporarily lost access to PC where I could do that. Now it’s restored, I’ll try that in next few days
ok, started fresh and it all works as expected. Nice one 😉
@A-Shevchenko sorry to hear that. We are here to support you, take care!
@evertonlperes I’m running it outside of WSL. Logs are attached, let me know if you want me to enable debug mode 1557.zip .