-
Notifications
You must be signed in to change notification settings - Fork 822
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
install.sh throws errors #715
Comments
Thanks for the report! I wasn't able to reproduce this, but I think I found a fix. Let me know if you still have the issue after #716 ships! |
That did the trick. I wonder if its better to source automatically as part of the install script so that the cmds are available immediately? |
Oh! Haven't thought of that, it's an interesting approach! |
Thanks for the bug report!
Describe the bug
The shell PATH is unset because of the install script throwing errors while installing in a Ubuntu 16.04/18.04 LXD container env:
Steps to reproduce
Expected behavior
A clear install and the PATH variable setup appropriately so that I can start using wasmer/wapm immediately.
Actual behavior
The wasmer.sh script file is created:
However, I need to explicitly
source wasmer.sh
in order to be able to use the appropriate cli cmds.Additional context
N/A
The text was updated successfully, but these errors were encountered: