This message was deleted.
# rancher-desktop
a
This message was deleted.
p
Rancher Desktop should be picking up your certs from the system automatically (that is, install it into the rancher-desktop environment on startup). If it's not working correctly, please let me know where your CA certs are on the Windows side? We should be picking up the
CA
and
ROOT
stores and copying them to
/usr/local/share/ca-certificates/rd-*.pem
in the WSL side.
For debugging, you can see the certs we pull by running
C:\Program Files\Rancher Desktop\resources\resources\win32\internal\wsl-helper.exe certificates
manually.
l
I haven't 100% confirmed it's ca cert issue or a proxy issue. I'm getting a
Error response from daemon: Get "<https://registry-1.docker.io/v2/>": EOF
on
docker pull hello-world
Should dns resolution work within the rancher-desktop distro? ie
wsl.exe -d rancher-desktop ping <http://google.com|google.com>
can't resolve google.com
p
Hmm. Try enabling network tunnel, as documented at https://docs.rancherdesktop.io/ui/preferences/wsl/network — that makes it do DNS on your host machine and forward the response into WSL
(We're aiming to make that the default soon, and the only thing soon after that; but it's still missing a feature)
l
certs look ok based on the output of that wsl-helper.exe command. I have network tunneling enabled. Just to confirm this command should work right?
wsl.exe -d rancher-desktop nslookup <http://google.com|google.com>
p
You will need
rdctl shell nslookup <http://google.com|google.com>
instead
(To get into our network namespace, avoiding issues with the main WSL one possibly having been changed by other distros and things like that)
l
if the rancher-desktop wsl container is stopped how do I restart it?
p
Start Rancher Desktop? (The main process does a bunch of setup in the WSL container, so just starting it from WSL wouldn't set things up correctly)