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

wasmer run-unstable . doesn't work #3812

Closed
syrusakbary opened this issue Apr 22, 2023 · 2 comments · Fixed by #3852
Closed

wasmer run-unstable . doesn't work #3812

syrusakbary opened this issue Apr 22, 2023 · 2 comments · Fixed by #3852
Assignees
Labels
priority-high High priority issue
Milestone

Comments

@syrusakbary
Copy link
Member

Running:

wasmer run-unstable .

Doesn't do anything the wasmer.io website (it just halts)

@syrusakbary syrusakbary added this to the v3.3 milestone Apr 22, 2023
@Michael-F-Bryan Michael-F-Bryan modified the milestones: v3.3, v4.0 May 2, 2023
@ptitSeb ptitSeb changed the title wasmer run-unstable wasmer run-unstable . doesn't work May 3, 2023
@ptitSeb
Copy link
Contributor

ptitSeb commented May 3, 2023

Probably related to #3748

@theduke theduke added the priority-high High priority issue label May 9, 2023
@Michael-F-Bryan
Copy link
Contributor

I did some troubleshooting and this seems to have been resolved in #3852.

$ sudo ~/.cargo/bin/wasmer run-unstable --net --mapdir /public:./out .

Note that I was originally getting this error because you need to pass in the --net flag and use sudo to listen on port 80.

$ ~/.cargo/bin/wasmer run-unstable .
2023-05-22T12:17:13.962139Z ERROR static_web_server::server: server failed to start up: failed to bind to [::]:80 address

Caused by:
    Not supported (os error 58)

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

Successfully merging a pull request may close this issue.

4 participants