This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Can you tell what specifically was the problem?
Just that you switched the docker context away from default, or something else?
r
ERROR: Cannot connect to the Docker daemon at unix:///Users/{user}/.colima/docker.sock. Is the docker daemon running?
I just rm’d .docker and it fixed it
f
You don't have the content of the old
~/.docker/config
anymore, maybe in the shell buffer?
I suspect it was just you setting
docker context use colima
and running
docker context use default
or
docker context use rancher-desktop
might have fixed it
Ah sorry, I missed that you posted the error above. That pretty much confirms that you were still using the colima context
r
I had not run any docker context commands. The Colima thing was from weeks ago.
f
Hmm, maybe colima automatically changes context for you
r
Not sure. I didn’t see anything in my .zshrc anyway
f
So it runs
docker context use colima
for you, and that information is persisted in
~/.docker/config.json
r
Thanks for the info. Maybe it’s too much of an edge case for an FAQ but it sure bit me 🙂
f
No, it is something that Rancher Desktop should detect and alert you too. I'm updating Add diagnostics to "Troubleshooting" page · Issue #2319 · rancher-sandbox/rancher-desktop with more ideas right now.
I think having some visual cue in the app (and maybe the tray icon) that something is misconfigured would be even more helpful than a FAQ entry because it would proactively alert you
🎯 1