Open thardie opened 2 years ago
I'm not sure how bash vs dash can affect this, since the download is happening from within rustup-init itself.
Does rustup install successfully on the host OS?
If you run rustup-init by hand within WSL does it still fail?
If you run whatever scenario fails with the env variable RUSTUP_DEBUG
set to 1
and add -v
to the command line options, what output do you get?
I got the same error on the same environment, and rustup NOT installed AFTER got error
$ type rustup
bash: type: rustup: not found
and sh(dash) got error, so change it to bash, then success
That looks like a PATH problem : when you started bash the bash profile gets loaded and now the already installed rustup is available for use.
Restarting dash should also have had the same effect.
Regardless @krmbn0576 please file a new bug for your issue, this bug is @thardie 's who reported the opposite case.
Problem
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | bash
fails with:Manual attempt:
This is under Ubuntu 20.04 LTS
Steps
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | bash
Possible Solution(s)
Surprisingly, launching the script with "sh" instead works! On my system, sh is a link to
dash
, so I'm guessing this is some interaction with bash versus dash. Could be useful to other troubleshootingNotes
This is running Ubuntu under WSL2.
Ubuntu network config:
Windows network config:
Rustup version
Installed toolchains