ld/nvm
1
0
Fork 0
mirror of https://github.com/nvm-sh/nvm.git synced 2025-05-10 14:21:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
added WSL Troubleshooting and provided a solution to a common problem (fixed typos)
This commit is contained in:
mattjaf 2022-11-30 19:38:33 -08:00 committed by GitHub
parent 11b308ae8b
commit d4bfd7d30d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@ -983,18 +983,19 @@ Now you should be able to use node as usual.
## WSL Troubleshooting
If you've encountered this error on wsl-2
If you've encountered this error on WSL-2
```sh
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh | bash
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:09 --:--:-- 0curl: (6) Could not resolve host: raw.githubusercontent.com
```
It may be due to your antivirus, vpn, or other reasons.
It may be due to your antivirus, VPN, or other reasons.
Where you can `ping 8.8.8.8` while you can't `ping google.com`
This could be simply be solved by running this in your root directory:
This could simply be solved by running this in your root directory:
```sh
sudo rm /etc/resolv.conf
@ -1004,13 +1005,13 @@ This could be simply be solved by running this in your root directory:
sudo chattr +i /etc/resolv.conf
```
which deletes your `resolve.conf` file thats automatically generated when u run WSL, creates a new file and puts `nameserver 8.8.8.8`, then creates a wsl.conf file and adds `[network]` and `generateResolveConf = false` to prevent auto generation of that file.
This deletes your `resolve.conf` file thats automatically generated when u run WSL, creates a new file and puts `nameserver 8.8.8.8`, then creates a `wsl.conf` file and adds `[network]` and `generateResolveConf = false` to prevent auto generation of that file.
You can check the contents of the file by running:
you can also run
```sh
cat /etc/resolv.conf
```
to check the contents of the file
## Maintainers