Default RADI endpoint not working on WSL2

[Bhardwaj-Himanshu]

Issue

Steps to reproduce
Launch an instance of docker container jderobot/robotics-academy:latest , the port redirects to https://0.0.0.8000/

Steps to reproduce
Launch an instance of docker container jderobot/robotics-academy:latest , the port redirects to https://0.0.0:8000/

Behaviour
Should show instance deployed at https://0.0.0.0:8000/--> which refuses to connect, instead I need to connect to https://127.0.1:8000/ manually!

[pawanw17]

Hi @Bhardwaj-Himanshu can you tell more about the system on which you are seeing this bug? Is it a VM? what kind of connections you have? ubuntu version?

[Bhardwaj-Himanshu]

The issue is observed on WSL2
No issues if I run it on a Ubuntu Machine or Ubuntu Cloud instance!

Also, it's my bad as well for misinterpreting the question.

[pawanw17]

Hi Sorry for delay, looking around this seems to be a known issue of wsl2
https://stackoverflow.com/questions/69926941/localhost-refused-to-connect-on-wsl2-when-accessed-via-https-localhost8000-b

https://abdus.dev/posts/fixing-wsl2-localhost-access-issue/

You can try one of the above solutions (there are more available I think) but I suggest just use to 127.0.0.1:8000 for WSL2 since this is more of a WSL2 issue than a Robotics Academy issue.

Robotics Academy uses 0.0.0.0 since that is also the default IP docker uses and also accepts any connections on 127.0.0.1 and if you see, it is hard coded at a lot of places,

@pariaspe @jmplaza thoughts?

[Bhardwaj-Himanshu]

No worries for the delay mate, no rush!
Also, yup now this clarifies some of my doubts regarding the same and how to get around it.
Thanks for the much-needed help.

@pawanw17

Also, just a out of curiosity question here, do you use wsl2 as your primary coding platform on windows as well? If yes, what CPU are you on? Cause my CPU even spikes at around 100% when building docker images!

Also I have manually configured to use only 2 cores out 8, but using a browser on windows and then building images in background sure does cause a hell lot of stress on the system.

[pawanw17]

I don't use windows much, I have a dual booted machine with ubuntu, and yeah building docker images does take some cpu power(gets the fans running).... If possible just use ubuntu(or any linux) for development, it'll save you from a lot of headaches.

I don't have any experience with wsl2.

[pariaspe]

I'm sorry guys, but I can't help you here. No clues about it

[Bhardwaj-Himanshu]

Yep, finally switched to ubuntu! and the transition was smooth I must say!
Also thanks for the support!