This message was deleted.

Are you running the rancher-desktop app during your testing? The links required are setup as the app initializes. If you are running the app, are you seeing any errors on the app?

Yes, after install the rancher GUI shows that the Helm charts are complete and all services are active. When rancher is down then the rancher-desktop distro in WSL2 is inactive, so I would not have been able to repeat the tests there. Notice that nerdctl and Docker are both available in the rancher distro, but not in Ubuntu. Also, it doesn't appear that systemd is available in either distro, which is likely, the cause of the issue. I'm hoping for a solution from someone who knows how to solve the issue properly, instead of cobbing a solution myself.

well systemd isn’t supported in WSL2 so if you need pid1 that will be a blocker. What is the Ubuntu distro role in your design? Sorry the wall of text makes it hard to follow. RD uses Alpine for the container host and you can call docker or nerdctl from Windows

sorry, brainfart - containerd not systemd.

it looks like you are doing a lot of calls from the Ubuntu dist. So assume you checked off the integration in that dist so it handles the networking between the two dists? I might suggest just doing some incremental tests from your CMD prompt to make sure the basics are working as well.

assume you checked off the integration in that dist so it handles the networking between the two dists?

I tried to determine the network status by pinging the IP's listed by ifconfig. Are there other steps you suggest?

I might suggest just doing some incremental tests from your CMD prompt to make sure the basics are working as well.

The basics of WSL? RD? What types of tests do you recommend? I'm new to WSL and K8s, so I'm still getting a handle on the details of the components, plumbing, etc. My intuition is that RD didn't install/link all of the components that were intended in either dist. I can install/link them manually, but I'm hoping that someone can provide the coorect configuration (e.g. "containerd is installed in dist x:path y, with a simlinks in dist x:path z, dist a:path b"). Then I can correct the configuration without breaking the intended integration.