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 . --net --entrypoint=abc doesn't work #4691

Open
syrusakbary opened this issue May 14, 2024 · 2 comments
Open

wasmer run . --net --entrypoint=abc doesn't work #4691

syrusakbary opened this issue May 14, 2024 · 2 comments
Assignees
Milestone

Comments

@syrusakbary
Copy link
Member

Wasmer entrypoint doesn't work.

Steps:

  1. Clone https://github.com/wasmer-examples/laravel-wasmer-starter
  2. Run wasmer run . --net --entrypoint=artisan
  3. It doesn't do anything -> It should show

It should show something like:

$ wasmer run . --net --entrypoint=artisan
wasm execute failed [/bin/sh] - could not find binary '/bin/sh'
wasm execute failed [/usr/local/bin/stty] - could not find binary '/usr/local/bin/stty'
wasm execute failed [/usr/local/bin/stty] - could not find binary '/usr/local/bin/stty'
Laravel Framework 11.7.0

Usage:
  command [options] [arguments]

Options:
 ...

You can check the right output if you change in wasmer.toml the entrypoint from php to artisan

@syrusakbary syrusakbary added this to the v4.3.1 milestone May 14, 2024
@theduke
Copy link
Contributor

theduke commented May 14, 2024

I recently tested --entrypoint and it worked fine in a package with multiple entrypoints.

Might be a combination of issues here.

@syrusakbary
Copy link
Member Author

We tested again, on @maminrayej laptop and things worked well... I need to retry locally and see what's going on. Lets put this on halt until I retest

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

3 participants