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

Cargo install fails with musl rust #136

Closed
arb000r opened this issue Jun 23, 2022 · 4 comments · Fixed by #138
Closed

Cargo install fails with musl rust #136

arb000r opened this issue Jun 23, 2022 · 4 comments · Fixed by #138

Comments

@arb000r
Copy link

arb000r commented Jun 23, 2022

Hey all,

Trying to build a docker image as per docs with clux/muslrust stable. However everytime results in

------                                                                                                                                                         
 > [planner 1/3] RUN cargo install cargo-chef:                                                                                                                 
#9 0.763     Updating crates.io index
#9 18.12 Killed
------
executor failed running [/bin/sh -c cargo install cargo-chef]: exit code: 137```
@louneskmt
Copy link
Contributor

See this rust-lang/cargo#10781.

@LukeMathWalker Is there a way to add a flag to use unstable features (like -Z <unstable-feature> on cargo build) with cook?

@LukeMathWalker
Copy link
Owner

That'd be desirable, but it's not currently possible.

@louneskmt
Copy link
Contributor

See #137.

@LukeMathWalker
Copy link
Owner

@1saf: this is not an issue with cargo-chef, but rather an issue with cargo itself.

You have three workarounds:

  • Use nightly: cargo +nightly -Z sparse-registry install cargo-chef;
  • Use a prebuilt image that comes with cargo-chef already installed;
  • Use CARGO_NET_GIT_FETCH_WITH_CLI=true cargo install cargo-chef to use an alternative method to fetch the registry.

The sparse-registry should solve this problem for good, but it's not stable yet.

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

Successfully merging a pull request may close this issue.

3 participants