This message was deleted.
# rancher-desktop
a
This message was deleted.
1
w
are you in a proxy environment? Have you tries to use rdctl shell and see if you can access anything outside the VM?
👀 1
🙏 1
w
No proxy
I just tried swtching to docker desktop and everything works… switch back, it’s all broken agin 🤔
f
Not sure how you are running both Rancher Desktop and Docker Desktop. If you did not enable admin access, then you may need to set the docker context explicitly with
docker context use rancher-desktop
Actually, your problem doesn't seem to be with finding the socket, but with DNS resolution; not sure what may be causing this. Can you run regular docker containers, e.g.
docker run hello-world
, or does that fail too?
w
yeah it seems like a networking issue where traffic can't egress the rancher WSL instance so basic stuff is breaking. when you are in a rdctl shell can you do simple things like DNS via host calls, ping, curl to other endpoints
f
Also: is this using the "networking tunnel" feature (Network (Windows) | Rancher Desktop Docs). Does the behaviour change when you toggle the setting (and apply the change)?
w
This is on Mac OS
Let me try a few of those things 🙂
Copy code
ee@Lees-MacBook-Pro gitlab-compose-kit % docker run hello-world
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get "<https://registry-1.docker.io/v2/>": context deadline exceeded (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
Copy code
lee@Lees-MacBook-Pro gitlab-compose-kit % docker context use rancher-desktop
rancher-desktop
Current context is now "rancher-desktop"
lee@Lees-MacBook-Pro gitlab-compose-kit % docker run hello-world            
Unable to find image 'hello-world:latest' locally
docker: Error response from daemon: Get "<https://registry-1.docker.io/v2/>": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
f
Does this work:
Copy code
$ rdctl shell curl -I <https://registry-1.docker.io>
HTTP/1.1 404 Not Found
content-type: text/plain; charset=utf-8
docker-distribution-api-version: registry/2.0
x-content-type-options: nosniff
date: Thu, 09 Nov 2023 19:46:47 GMT
content-length: 19
strict-transport-security: max-age=31536000
w
Copy code
lee@Lees-MacBook-Pro gitlab-compose-kit % rdctl shell curl -I <https://registry-1.docker.io>
curl: (6) Could not resolve host: <http://registry-1.docker.io|registry-1.docker.io>
Error: exit status 6
And thank you 🙏 Really appreciate the help
f
But it works from the host shell? In which case DNS is broken inside the VM
w
I figure i’m going to kick myself when I figure out what’s up
Absolutely:
Copy code
lee@Lees-MacBook-Pro gitlab-compose-kit % rdctl shell curl -I <https://registry-1.docker.io>
curl: (6) Could not resolve host: <http://registry-1.docker.io|registry-1.docker.io>
Error: exit status 6
lee@Lees-MacBook-Pro gitlab-compose-kit % curl -I <https://registry-1.docker.io>
HTTP/1.1 404 Not Found
content-type: text/plain; charset=utf-8
docker-distribution-api-version: registry/2.0
x-content-type-options: nosniff
date: Thu, 09 Nov 2023 19:48:24 GMT
content-length: 19
strict-transport-security: max-age=31536000
f
Are you using VZ or QEMU?
w
VZ
f
Can you switch to QEMU, just for testing?
w
Of course 👍
Same result
f
Not really sure what to try next 😞 Does
resolv.conf
look correct?
Copy code
$ rdctl shell cat /etc/resolv.conf
nameserver 192.168.5.3
(it will be
...5.2
when using VZ)
w
Copy code
lee@Lees-MacBook-Pro gitlab-compose-kit % rdctl shell cat /etc/resolv.conf
search tickett.home
nameserver 192.168.5.2
f
I assume you switched back to VZ already, right?
w
No, I haven’t actually 🤔
f
That is weird; did the VM restart after making the change?
w
Yup
f
Do you have anything in the VM you need to keep, or can you try to do a factory-reset?
w
Can definitely try a factory reset
f
Let's try that and start with the default settings
w
Boom- fixed- thank you 🙏
I am kicking myself for not trying that earlier
I thought it’d just reset the settings liek VZ etc
But I guess it does more than tha 🤷
I’ll upgrade back to 1.11.0 now and see if it breaks again
f
Yeah, no idea why this happened, but glad it is fixed now
w
My guess it was the upgrade to sonoma?
f
I don't think so; I have a Sonoma machine, and it works fine for me 🤷
w
Yup- still happy after updating to 1.11.0 Thanks again- really appreciate it 🚀
f
You are welcome; glad it continued to work!