i need help that after uninstalling all docker des...
# rancher-desktop
w
i need help that after uninstalling all docker desktop, and try to rancher desktop the path for docker is not working, i tried using factory reset but still not working, can someone help me
b
@witty-city-90946 - Rancher Desktop uses containerd by default. So, you don't have Docker CLI available. You have nerdctl. You can switch to dockerd, but I'd recommend the better solution is to alias nerdctl to docker in your terminal's config file. Should be something like:
Copy code
Set-Alias -Name docker -Value nerdctl
Another suggestion I'd make is to use WSL for any development work in Windows.
f
No, the
docker
CLI should always be available (but may not work if the container engine is not set to
dockerd
.
@witty-city-90946 Did you open a new terminal window after installing Rancher Desktop? Because the installer cannot change the
PATH
for existing processes; it will only be effective for processes started after the installation has finished.
b
@fast-garage-66093 - Ah. Ok. This is a constant source for confusion though. I do believe, docker CLI should only be installed if dockerd is selected as the container runtime. My 2 cents.
f
It is included in the application and put on the
PATH
with all the other utilities. Adding/removing it whenever the user changes the container engine makes it even more confusing, because then the user will have to restart all terminal windows before the change becomes active. Inconvenient and easy to forget.
b
That could easily be put in as a remark in the change process in RD, once it is done. "As part of the container runtime change, we've installed X cli and updated
paths
accordingly. Please remember to restart any open terminals to see these changes."
f
Yeah, but how is this better than not having to do anything? 😄 What is the issue with having
docker.exe
on your
PATH
if you are not using it anyways?
b
Because users don't realize RD uses containerd and end up with this error.
It's what I thought this issue was similar to.
f
Yeah, but the user actively selected
containerd
, so seems to be confused anyways. And they would just get a different error message when they try to run
docker
and it is not on the
PATH
, so they would still be confused. Unless we wrap the tool with a shim that detects this.
b
I haven't installed RD for a while now. Is there a selection during installation?
If there is, this also assumes the user understands the difference between the two runtimes, which isn't always the case.
f
Yes, the first-run dialog looks like this (and
dockerd
is the default)
On Windows you don't get the
PATH
config options because the
PATH
is setup by the installer and not the app
b
Hmm... ok. Interesting. I could swear when I installed RD many moons ago, containerd was default. It was at a time where I had a large knowledge gap in k8s too. 😛 Like 3 years ago. I haven't used RD much since either, as I have a remote development setup in a k8s cluster setup up on bare metal servers. 🤷‍♂️ So, I apologize for misinformation. I need to fix my reply.
In that other thread.
f
The default was switched to
dockerd
in Release Rancher Desktop 1.9 from June 2023.
You only get the first-run dialog after the initial install, or after a factory-reset.
b
Aha! Ok. My bad. Sort of. 😁
You wouldn't happen to have knowledge in Rancher too, would you? I have an issue with Rancher.