rancher-sandbox / rancher-desktop

Container Management and Kubernetes on the Desktop
https://rancherdesktop.io
Apache License 2.0
5.96k stars 281 forks source link

WSL2: Waiting for image manager to be ready in "images" page #7649

Open don4get opened 4 days ago

don4get commented 4 days ago

Actual Behavior

Images from WSL2 Ubuntu 24.04 are not seen in Rancher desktop. In "images" page, following text is displayed: "Waiting for image manager to be ready"

Steps to Reproduce

Result

No images are seen in Rancher desktop

Expected Behavior

Images built and downloaded in WSL2 distro are shared with rancher desktop

Additional Information

I tried the following:

The images.log shows the following result:

error during connect: Head "
[http://localhost:2375/_ping"](http://localhost:2375/_ping%22)
: dial tcp [::1]:2375: connectex: No connection could be made because the target machine actively refused it.

If I run a container inside WSL, it is seen in "Containers" page of Rancher desktop.

Rancher Desktop Version

1.16.0

Rancher Desktop K8s Version

None

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

Windows 11 / WSL2 / Ubuntu 24.04

What CPU architecture are you using?

x64

Linux only: what package format did you use to install Rancher Desktop?

None

Windows User Only

No response

Nino-K commented 3 days ago

@don4get The issue here could be because we provide and manage our own instance of Docker (Moby) backend. If another instance is running, it could cause a conflict. I suggest uninstalling the Docker instance in WSL while RD is not installed, or consider performing a factory reset after uninstalling Docker to make sure everything works as expected.

don4get commented 2 days ago

@don4get The issue here could be because we provide and manage our own instance of Docker (Moby) backend. If another instance is running, it could cause a conflict. I suggest uninstalling the Docker instance in WSL while RD is not installed, or consider performing a factory reset after uninstalling Docker to make sure everything works as expected.

Thank you Nino, I will try and update this comment when it's done.

don4get commented 2 days ago

@Nino-K I uninstalled everything related to docker:

sudo apt-get purge -y docker-engine docker docker.io docker-ce docker-ce-cli docker-compose-plugin
sudo apt-get autoremove -y --purge docker-engine docker docker.io docker-ce docker-compose-plugin

sudo rm -rf /var/lib/docker /etc/docker
sudo rm /etc/apparmor.d/docker
sudo groupdel docker
sudo rm -rf /var/run/docker.sock
sudo rm -rf /var/lib/containerd
sudo rm -r ~/.docker

On windows side, I also deleted: C:\Users\xxx\AppData\Local\Docker

Then I tried to :

In all these cases, I did not get anything in "Images page", with the same error of connection to port 2375 in images log.

After that I also tried to install moby in wsl2 Ubuntu image -> no positive inpact on Rancher desktop, even after reinstall / factory reset.

Finally I tried to create a /etc/docker/daemon.json in WSL2 image, to disable TLS:

  "debug": false,
  "tls": false,
  "hosts": ["tcp://127.0.0.1:2375"]

After daemon restart, still no result in images... I made sure WSL2/Ubuntu forward the 2375 port to Windows.

I don't know what else to do. Do you have an idea please?