Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add information on Windows support with WSL #555

Closed
yklcs opened this issue Oct 26, 2019 · 8 comments
Closed

Add information on Windows support with WSL #555

yklcs opened this issue Oct 26, 2019 · 8 comments

Comments

@yklcs
Copy link

yklcs commented Oct 26, 2019

image

Polynote works on Windows with WSL Ubuntu!
Might be worth it mentioning it in the README or website.

@yklcs yklcs changed the title q Add information on Windows support with WSL Oct 26, 2019
@jonathanindig
Copy link
Collaborator

Welcome @RocketLL, thanks for trying out Polynote and getting it working on Windows, that's great! We'd definitely welcome a PR with Windows instructions :)

@sho-87
Copy link

sho-87 commented Oct 29, 2019

@jonathanindig are there any plans for windows support without having to go through WSL?

@jonathanindig
Copy link
Collaborator

Hi @sho-87, PRs always welcome!

@ctivanovich
Copy link

@RocketLL I've got the server up and running in WSL 2, but can't seem to connect to it through chrome. Any extra set-up needed beyond the basic instructions?

@yklcs
Copy link
Author

yklcs commented Oct 30, 2019

@ctivanovich More details would help. Does the server start up normally? Which address are you connecting to?

@ctivanovich
Copy link

ctivanovich commented Oct 30, 2019

Yeah, it starts up normally, and I connect to the default address of 127.0.0.1:8192. All looks green in the console, no errors, just, page fails to load in the browser, Chrome's ERR_CONNECTION_REFUSED. I regularly run local servers on this machine, so firewall shouldn't be an issue.

Output of netstat:

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp6       0      0 127.0.0.1:8192          :::*                    LISTEN      478/java

@ctivanovich
Copy link

Any updates on this?

@jeremyrsmith
Copy link
Contributor

@ctivanovich see #671 – I guess WSL is in a container, so its network is sandboxed; if you listen on 0.0.0.0 then it apparently works.

Also see microsoft/WSL#4338 (comment) – looks like the underlying issue is fixed after WSL build 18970+ (so you wouldn't even need to configure the listen address)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants