On a Ubuntu 20.04 server - I've also tried removing and reinstalling curl as per This SO answer.
is also open.. So no idea how to install Node v14 LTS under nvm now..
Asked
Active
Viewed 428 times
0
-
2Is this happening inside a VirtualBox VM by any chance? – szx May 29 '21 at 11:54
-
Where are you from? Maybe your Internet connection has been censored. – pan93412 May 29 '21 at 11:55
-
@pan93412 Nope. Internet connection is absolutely fine. – Storm May 30 '21 at 13:27
-
@szx Yes. But everything else is working A-Ok. Even node v12 downloaded and installed properly before. – Storm May 30 '21 at 13:27
-
1@Storm there is a bug in VirtualBox 6 that leads to corruption of downloaded files, try updating to the latest version and disabling Hyper-V, or just use VirtualBox 5. – szx May 30 '21 at 20:03
-
1https://www.virtualbox.org/ticket/19695?cversion=0&cnum_hist=6 – szx May 30 '21 at 20:04
-
is this a reinstall? If so, does NVM have an option similar to --reinstall? – Nate T Jun 05 '21 at 07:51
3 Answers
0
The readme on the github for NVM says to use the provided install script for Linux installs. This can be achieved with curl or wget:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
I recommend that you click the link and read, as their is quite a bit of related info there.
Nate T
- 727
- 5
- 21
0
I was interested and just tested it out in a clean docker container (ubuntu:20.04) (as I dont use node that often), and it looked pretty straight forward:
apt-get update -y
apt-get install -y curl
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
source ~/.bashrc
nvm version
# none
nvm install --lts --default
nvm version
# v14.17.0
If it not that, then I would also assume, that the issue is related to your general environment, like network inspection, proxy access or else.
nicht-vergessen
- 365
- 2
- 5
0
As it is visible from the logs, the checksum process keeps failing in a repeated manner. And there have been issues highlighting that some ISO images can show issue with hashing process due to Windows 10 components. , which implicitly effects the checksum process under a guest environment on VirtualBox.
You can complete the steps provided by VirtualBox team there to resolve this issue, as pointed out on Virtual Box's forum:
it's Hyper-V that is causing the checksum problem you posted about, not the version of Virtualbox.
Gaurav Tiwari
- 349
- 2
- 7