-
Notifications
You must be signed in to change notification settings - Fork 192
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
Run cargo build on MacOS(M1), it be killed when Updating crates.io index #151
Comments
I'm seeing the same issue |
I'm currently having the same issue :/ |
I got a static binary build to work on my M1 mac using the rust-musl-builder image. Here is my Dockerfile:
|
@letsgetrusty Thanks a lot ! Just so you know, I jumped on the Rust train 2 days ago mainly thanks to your videos so I wanted to address a massive thank you for your work to welcome new rustacean on board. |
@letsgetrusty I did not expect to see this name here. However, I just wanted to say, you are seriously the best! |
What did you try to do?
alias rust-musl-builder='docker run --rm -it -v "$(pwd)":/home/rust/src ekidd/rust-musl-builder:latest'
rust-musl-builder cargo build --release
What happened?
╰─$ rust-musl-builder cargo build --release
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
Updating crates.io index
%
I run docker run directly, and got:
docker run --rm -it -v "$(pwd)":/home/rust/src ekidd/rust-musl-builder:latest 137 ↵
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.
rust@9e4d8a501d78:
/src$ ls/src$ cargo buildCargo.lock Cargo.toml logs release.sh src target
rust@9e4d8a501d78:
Updating crates.io index
Killed Fetch [======> ] 30.75%, 2.60MiB/s
What did you hope to happen?
finish building
Additional information
The text was updated successfully, but these errors were encountered: