Hi All. Quick question. We had a dev who started RD ran docker-compose up and was working fine. Accidentally started another instance of RD which failed and so then he quit that. BUT at this point the only way to connect again to the services that were exposed was to reboot his PC, start RD and run docker-compose. Things that were tried before the reboot were like docker compose down and then back up. Has anyone else seen this behavior? Should I open issue on GitHub? Thanks!

mac, linux, windows?

Windows 11

so wsl2 at play. I have seen on my windows machine that WSL does not drop the WSL vswitch even after all WSL machines are shutdown. That could keep those port forwarding rules live possibly. I would see if rebooting the WSL adapter cleans things up if it occurs again

thanks Justin, just to verify so something docker compose down, quit RD and then "wsl -- shutdown" and then re-launch RD, etc...

no shutdown I find doesn’t reclaim the vswitch (its provisioned on demand when you first launch WSL for that uptime session). I have had other routing issues though w WSL so in your Network Adapters you should see a vEthernet (WSL) and you can stop/start that which for me sets the vSwitch back to a known good

Thank you for the help! We'll give this a try next time it happens