rancher-desktop cli missing in Windows terminal

[ulkas]

Actual Behavior

after a generic windows update i suddenly lost the terminals for ubuntu (wsl), rancher-desktop and rancher-desktop-data.
a hint might be that when i opened the wsl terminal from windows menu directly, it prompted me to enter new superuser and password for ubuntu, like it was a fresh installation after the windows update. after that im able to see the ubuntu cli but still no rancher.
reinstalling rancher didnt help. deleting the settings.json in windows terminal also didnt help.

Steps to Reproduce

none

Result

access to the rancher-desktop terminal window

Expected Behavior

rancher-desktop shall be listed in the windows terminal list

Additional Information

No response

Rancher Desktop Version

1.9.1

Rancher Desktop K8s Version

1.23.8

Which container engine are you using?

moby (docker cli)

What operating system are you using?

Windows

Operating System / Build Version

windows 10 enterprise 21H2

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

[ulkas]

adding output of the wsl --list --verbose command in PS:

[mook-as]

Unfortunately we're not doing anything there (we didn't even add it to Windows Terminal, it just picked it up because it's a WSL distribution). Which is to say, you might need to ask the Windows Terminal folks about it. Sorry about that.

If anything, we need to at some point implement making Windows Terminal skip rancher-desktop-data (since everybody, including our app, should be accessing it via rancher-desktop) anyway…

[jandubois]

If anything, we need to at some point implement making Windows Terminal skip rancher-desktop-data

This has actually been implemented in Windows Terminal now, and is the reason both distros are no longer listed: microsoft/terminal#15166.

So the behaviour reported in this issue is intentional.

The only supported mechanism to run a shell in the rancher-desktop distro is via rdctl shell because that also takes care of setting up the correct network namespace etc.