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
[BUG] Dock run error on windows (Cargo.toml) #74
Comments
Hey, thanks for the bug report, as soon as we get some time we'll check it! |
I managed to find where the code is located. It is located in the deployment.js file in the storeCode function. The following code is called:
If I remove the second line of the code and replace ¨$(pwd)" with "%cd%", then I get a built and a deployment though not 100 % correct because the second line was removed of course. So what I get is:
But the part |
I fixed the basename error as well. This is my solution for windows environments:
|
Hey @ToniBar, sorry for the delay here! Have you tried running Terrain with WSL, or is there a reason why you wouldn't be able to use WSL? In our experience using WSL can avoid these types of issues. |
Closing, please reopen if you're still having issues! |
Issue description
I try to run
npx terrain deploy counter --signer validator
in windows. This fails with error message on $(pwd).Steps to reproduce the issue
npx terrain deploy counter --signer validator
in windows.See 'docker run --help'.
Error: Command failed: docker run --rm -v "$(pwd)":/code --mount type=volume,source="$(basename "$(pwd)")_cache",target=/code/target --mount type=volume,source=registry_cache,target=/usr/local/cargo/registry
cosmwasm/rust-optimizer:0.12.5
Tools and operating system versions
Operating system: windows 10
From what I found the error is caused because windows doesn't recognize $(pwd) and it should be %cd% instead. The
docker -run
call leading to this error can be found under folder /counter in file Cargo.toml. Modifying pwd to cd in this file doesn't work because this file is regenerated after every run. I have for the moment no idea where this generation happens so I am not able to modify pwd.The text was updated successfully, but these errors were encountered: