-
Notifications
You must be signed in to change notification settings - Fork 858
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
nginx doesn't seem to work in 1.0.0 #1997
Labels
bug
Something isn't working
Comments
Thanks for reporting this! It seems we changed some semantics when refactoring part of our emscripten implementation, I'll look into this a bit more |
1 task
bors bot
added a commit
that referenced
this issue
Jan 11, 2021
2005: Improve WasmerEnv, fix emscripten imports r=syrusakbary a=MarkMcCaskey This PR adds two new features to `WasmerEnv`: - `alias = "alias_name"` for specifying additional names to try to find the export by - `optional = true` for specifying that failure to find this export is okay In addition, it fixes some breakages on emscripten introduced by migrating emscripten to `WasmerEnv` naively. I've tested this in `examples/nginx` on the `0.x` branch and Wasmer is able to run nginx again, so this resolves #1997 # Review - [x] Add a short description of the the change to the CHANGELOG.md file Co-authored-by: Mark McCaskey <mark@wasmer.io>
bors bot
added a commit
that referenced
this issue
Jan 11, 2021
2005: Improve WasmerEnv, fix emscripten imports r=MarkMcCaskey a=MarkMcCaskey This PR adds two new features to `WasmerEnv`: - `alias = "alias_name"` for specifying additional names to try to find the export by - `optional = true` for specifying that failure to find this export is okay In addition, it fixes some breakages on emscripten introduced by migrating emscripten to `WasmerEnv` naively. I've tested this in `examples/nginx` on the `0.x` branch and Wasmer is able to run nginx again, so this resolves #1997 # Review - [x] Add a short description of the the change to the CHANGELOG.md file Co-authored-by: Mark McCaskey <mark@wasmer.io>
bors bot
added a commit
that referenced
this issue
Jan 11, 2021
2005: Improve WasmerEnv, fix emscripten imports r=MarkMcCaskey a=MarkMcCaskey This PR adds two new features to `WasmerEnv`: - `alias = "alias_name"` for specifying additional names to try to find the export by - `optional = true` for specifying that failure to find this export is okay In addition, it fixes some breakages on emscripten introduced by migrating emscripten to `WasmerEnv` naively. I've tested this in `examples/nginx` on the `0.x` branch and Wasmer is able to run nginx again, so this resolves #1997 # Review - [x] Add a short description of the the change to the CHANGELOG.md file Co-authored-by: Mark McCaskey <mark@wasmer.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I thought I'd try nginx to try out the new Wasm container awesomeness, but it doesn't work well, or not at all:
Steps to reproduce
Expected behavior
An HTTP server servin' my pages.
Actual behavior
Emscripten not being available?
Additional context
This is on macOS BS Intel.
The text was updated successfully, but these errors were encountered: