is there a way to fix these issues? I already hav...
# rancher-desktop
o
is there a way to fix these issues? I already have docker desktop running.
docker context ls
shows default not the docker-desktop context
p
• For the first one:
docker context ls
shows
default
is selected, not
desktop-linux
(which isn't a thing we set, so presumably you had Docker Desktop installed)? Is that set via the
DOCKER_CONTEXT
environment variable or anything like that? (Please check with Start → Edit environment variables for your account) • For the second one: please see the logs, particularly
integrations.log
. • For the third one, please follow the text (or if you don't care about Kubernetes, disable it). Note that running Docker Desktop at the same time as Rancher Desktop isn't going to work.
f
You can try to use
docker context use default
to switch back to the default named pipe interface (for running docker.exe in a Windows shell)
o
docker context ls
shows I am using the default context
Copy code
docker context ls                                                                                             ✔ │ 06:57:49 AM  
NAME            DESCRIPTION                               DOCKER ENDPOINT                             ERROR
default *       Current DOCKER_HOST based configuration   unix:///var/run/docker.sock
desktop-linux   Docker Desktop                            npipe:////./pipe/dockerDesktopLinuxEngine
p
I'm confused, why is
default
using
unix://
instead of
npipe://
? I thought this was on Windows, so
unix://
doesn't even make sense (WSL kind of has support for Unix named pipes now, but my understanding is that it doesn't work well.)
o
hmm, so I found the issue(I don't think its an issue per se). looking at the context from powershell it was using docker-desktop but from within wsl2 it was default. I don't know the exact reasoning they are doing it this way though