rami3l

@rbtcollins Moving forwards I suggest we either: 1. Implement `rustup which --prefix` which gives `~/.rustup/toolchains//bin` and let the user handle the rest. 2. Implement something like `rustup component list --verbose`...

@sohang3112 Thanks a lot for your support! ... but you haven't answered my question yet: > May I ask what you are using these paths for? Your original motivation is...

> @rami3l Is there any update on this issue? @sohang3112 The plan is to finish this in the v1.28.0 release cycle, but as my life plans have suddenly changed and...

> if I issue > > > $ rustup default stable-i686-unknown-linux-gnu > > then it solves the issue, I'd prefer the image to not have workaround, the same image builds...

@smoothdeveloper You're running 64-bit Linux as your Docker host then. However, `~/.cargo/bin/rustc` is not `rustc`, but `rustup`. If I have correctly understood your situation, you have downloaded a 32-bit `rustup`...

@smoothdeveloper We are making progress then, thank you! Would you mind running the script again with the verbose mode on, e.g. with something like `sh -x`? If there is a...

@djc Back in v1.26.0 rustup would happily accept x64 as a native host and we have got a lot for surprising behaviors because of that (mostly linkage errors). That's why...

@nic-hartley Just to clarify, we do have download resuming in Rustup today. However, I think you might have encountered a case where that cache got invalidated, and if so, we...

@rochdev Does our new 1.27 version (https://internals.rust-lang.org/t/seeking-beta-testers-for-rustup-1-27-0/20352) work for you?

@rochdev Thanks for your report! The thing here is that we're currently considering the removal of the cURL backend (possibly as early as in 1.28), so it's a must that...