-
Notifications
You must be signed in to change notification settings - Fork 3
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
m1 mac/arm docker environment setup #146
Comments
Tried disabling wasm-opt as suggested in the original error message, but was unsuccessful (don't really know how to use Cargo.toml). First tried adding to Cargo.toml in my local repo cloned from Matico repo (the second Cargo.toml edit based on https://rustwasm.github.io/docs/wasm-pack/cargo-toml-configuration.html). Both attempts to no avail - same error for the first attempt, and the second attempt produced the following: `=> ERROR [rust-builder 20/31] RUN cargo build --release
failed to solve: executor failed running [/bin/sh -c cargo build --release]: exit code: 101 |
Hey @TyceHerrman Thanks for the bug report. I unfortunately don't have an M1 mac to reproduce this but @nofurtherinformation does. He is away on holiday for a little bit but when he gets back I can ask him to take a look at this. We are revamping the way we do builds this week. There is a good chance the tweaks will fix this problem. Will ping you when it's merged to give it a go. |
Tried this again today and am now getting the same issue as #148. Found this https://stackoverflow.com/questions/72061535/getting-this-error-message-while-installing-solana-error-failed-to-run-custom, which after completing the steps described, allowed me to run first step of individual components |
While using the docker-compose up environment setup, I receive the following warning (not sure if it's relevant) and error on my m1 mac:
This seems to be related to this issue with wasm-pack: rustwasm/wasm-pack#913.
It looks like it was addressed in wasm-pack v0.10.2: https://github.com/rustwasm/wasm-pack/releases/tag/v0.10.2
I'm not able to definitively determine which version of wasm-pack Matico is using, but it looks like in the Dockerfile that it's pulling the latest version from the wasm-pack github repo (I could be misinterpreting that though). If that's the case, not sure why this error would occur.
The text was updated successfully, but these errors were encountered: