Installation fails on WSL2

[ellistalley]

Operating system and version:

Windows 11 Home 24H2 build.26100.6584
WSL version: 2.5.10.0
Kernel version: 6.6.87.2-1
WSLg version: 1.0.66
MSRDC version: 1.2.6074
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.6584
OS: Debian GNU/Linux 13 (trixie) x86_64
Host: Windows Subsystem for Linux - Debian (2.5.10.0)
Kernel: Linux 6.6.87.2-microsoft-standard-WSL2
Shell: bash 5.2.37
WM: WSLg 1.0.66 (Wayland)
Terminal: Windows Terminal
CPU: AMD Ryzen 7 5700U (16) @ 1.80 GHz
GPU: AMD Radeon(TM) Graphics (495.56 MiB) [Integrated]
Memory: 527.80 MiB / 7.43 GiB (7%)
Swap: 0 B / 2.00 GiB (0%)
Disk (/): 2.21 GiB / 1006.85 GiB (0%) - ext4
Disk (/mnt/c): 216.84 GiB / 459.57 GiB (47%) - 9p

nvm debug output:

N/A

nvm ls output:

N/A

How did you install nvm? curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash

What steps did you perform?

Copy pasted curl command

What happened?

Installation failed. Git cloning tried to allocate 20GB via malloc, failed.

=> Downloading nvm from git to '/home/ellis/.nvm'
=> Cloning into '/home/ellis/.nvm'...
fatal: Out of memory, malloc failed (tried to allocate 21474836480 bytes)
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Failed to clone nvm repo. Please report this!

What did you expect to happen?

NVM installation success.

Is there anything in any of your profile files that modifies the PATH? No

If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out?

* Host nodejs.org:443 was resolved. * IPv6: 2606:4700:10::ac42:8046, 2606:4700:10::6814:1fc * IPv4: 172.66.128.70, 104.20.1.252 * Trying [2606:4700:10::ac42:8046]:443... * Immediate connect fail for 2606:4700:10::ac42:8046: Network is unreachable * Trying [2606:4700:10::6814:1fc]:443... * Immediate connect fail for 2606:4700:10::6814:1fc: Network is unreachable * Trying 172.66.128.70:443... * ALPN: curl offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / RSASSA-PSS * ALPN: server accepted h2 * Server certificate: * subject: CN=*.nodejs.org * start date: Mar 12 00:00:00 2025 GMT * expire date: Apr 12 23:59:59 2026 GMT * subjectAltName: host "nodejs.org" matched cert's "nodejs.org" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * Connected to nodejs.org (172.66.128.70) port 443 * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://nodejs.org/dist/ * [HTTP/2] [1] [:method: HEAD] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: nodejs.org] * [HTTP/2] [1] [:path: /dist/] * [HTTP/2] [1] [user-agent: curl/8.14.1] * [HTTP/2] [1] [accept: */*] * [HTTP/2] [1] [accept-encoding: deflate, gzip, br, zstd] > HEAD /dist/ HTTP/2 > Host: nodejs.org > User-Agent: curl/8.14.1 > Accept: */* > Accept-Encoding: deflate, gzip, br, zstd > * Request completely sent off * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): < HTTP/2 200 HTTP/2 200 < date: Mon, 06 Oct 2025 15:32:41 GMT date: Mon, 06 Oct 2025 15:32:41 GMT < content-type: text/html content-type: text/html < content-encoding: br content-encoding: br < cache-control: public, max-age=3600, s-maxage=14400 cache-control: public, max-age=3600, s-maxage=14400 < last-modified: Thu, 25 Sep 2025 19:48:29 GMT last-modified: Thu, 25 Sep 2025 19:48:29 GMT < vary: Accept-Encoding vary: Accept-Encoding < strict-transport-security: max-age=31536000; includeSubDomains; preload strict-transport-security: max-age=31536000; includeSubDomains; preload < x-content-type-options: nosniff x-content-type-options: nosniff < server: cloudflare server: cloudflare < cf-ray: 98a6367c9ef6b118-KIX cf-ray: 98a6367c9ef6b118-KIX <

• Connection #0 to host nodejs.org left intact

[ellistalley]

I have found a workaround which simply clones the repository to ~/.nvm using regular git clone (without the install script), then running the install script after manual cloning (the install script recognizes the already cloned .nvm folder).

Installation was successful after workaround.

[ljharb]

That's very strange; the repo isn't that large. what version of git do you have?

[ellistalley]

git version 2.47.3

[ljharb]

is it installed inside wsl? or is it a windows binary that wsl2 can execute?

[ellistalley]

git itself is installed inside wsl debian, via apt.

I'm trying to install nvm in wsl using the install script.

[freedomfraternity1822-ux]

podemo me explicar pede varias funcionalidades como vou ganhar dinheiro

…

On Mon, Oct 6, 2025 at 12:37 PM ellistalley ***@***.***> wrote: *ellistalley* created an issue (nvm-sh/nvm#3675) <#3675> Operating system and version: Windows 11 Home 24H2 build.26100.6584 WSL version: 2.5.10.0 Kernel version: 6.6.87.2-1 WSLg version: 1.0.66 MSRDC version: 1.2.6074 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26100.1-240331-1435.ge-release Windows version: 10.0.26100.6584 OS: Debian GNU/Linux 13 (trixie) x86_64 Host: Windows Subsystem for Linux - Debian (2.5.10.0) Kernel: Linux 6.6.87.2-microsoft-standard-WSL2 Shell: bash 5.2.37 WM: WSLg 1.0.66 (Wayland) Terminal: Windows Terminal CPU: AMD Ryzen 7 5700U (16) @ 1.80 GHz GPU: AMD Radeon(TM) Graphics (495.56 MiB) [Integrated] Memory: 527.80 MiB / 7.43 GiB (7%) Swap: 0 B / 2.00 GiB (0%) Disk (/): 2.21 GiB / 1006.85 GiB (0%) - ext4 Disk (/mnt/c): 216.84 GiB / 459.57 GiB (47%) - 9p nvm debug output: N/A nvm ls output: N/A How did you install nvm? curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash What steps did you perform? Copy pasted curl command What happened? Installation failed. Git cloning tried to allocate 20GB via malloc, failed. => Downloading nvm from git to '/home/ellis/.nvm' => Cloning into '/home/ellis/.nvm'... fatal: Out of memory, malloc failed (tried to allocate 21474836480 bytes) fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Failed to clone nvm repo. Please report this! What did you expect to happen? NVM installation success. Is there anything in any of your profile files that modifies the PATH? No If you are having installation issues, or getting "N/A", what does curl -I --compressed -v https://nodejs.org/dist/ print out? * Host nodejs.org:443 was resolved. * IPv6: 2606:4700:10::ac42:8046, 2606:4700:10::6814:1fc * IPv4: 172.66.128.70, 104.20.1.252 * Trying [2606:4700:10::ac42:8046]:443... * Immediate connect fail for 2606:4700:10::ac42:8046: Network is unreachable * Trying [2606:4700:10::6814:1fc]:443... * Immediate connect fail for 2606:4700:10::6814:1fc: Network is unreachable * Trying 172.66.128.70:443... * ALPN: curl offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS change cipher, Change cipher spec (1): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 / X25519MLKEM768 / RSASSA-PSS * ALPN: server accepted h2 * Server certificate: * subject: CN=*.nodejs.org * start date: Mar 12 00:00:00 2025 GMT * expire date: Apr 12 23:59:59 2026 GMT * subjectAltName: host " nodejs.org" matched cert's "nodejs.org" * issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA * SSL certificate verify ok. * Certificate level 0: Public key type RSA (4096/152 Bits/secBits), signed using sha256WithRSAEncryption * Certificate level 1: Public key type RSA (2048/112 Bits/secBits), signed using sha384WithRSAEncryption * Certificate level 2: Public key type RSA (4096/152 Bits/secBits), signed using sha384WithRSAEncryption * Connected to nodejs.org (172.66.128.70) port 443 * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://nodejs.org/dist/ * [HTTP/2] [1] [:method: HEAD] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: nodejs.org] * [HTTP/2] [1] [:path: /dist/] * [HTTP/2] [1] [user-agent: curl/8.14.1] * [HTTP/2] [1] [accept: */*] * [HTTP/2] [1] [accept-encoding: deflate, gzip, br, zstd] > HEAD /dist/ HTTP/2 > Host: nodejs.org > User-Agent: curl/8.14.1 > Accept: */* > Accept-Encoding: deflate, gzip, br, zstd > * Request completely sent off * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): < HTTP/2 200 HTTP/2 200 < date: Mon, 06 Oct 2025 15:32:41 GMT date: Mon, 06 Oct 2025 15:32:41 GMT < content-type: text/html content-type: text/html < content-encoding: br content-encoding: br < cache-control: public, max-age=3600, s-maxage=14400 cache-control: public, max-age=3600, s-maxage=14400 < last-modified: Thu, 25 Sep 2025 19:48:29 GMT last-modified: Thu, 25 Sep 2025 19:48:29 GMT < vary: Accept-Encoding vary: Accept-Encoding < strict-transport-security: max-age=31536000; includeSubDomains; preload strict-transport-security: max-age=31536000; includeSubDomains; preload < x-content-type-options: nosniff x-content-type-options: nosniff < server: cloudflare server: cloudflare < cf-ray: 98a6367c9ef6b118-KIX cf-ray: 98a6367c9ef6b118-KIX < - Connection #0 to host nodejs.org left intact — Reply to this email directly, view it on GitHub <#3675>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BWERXZGRSK5ZFIC6UMNCA6D3WKEDBAVCNFSM6AAAAACINOA2POVHI2DSMVQWIX3LMV43ASLTON2WKOZTGQ4DOOBXGUZTQNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ljharb]

what do the following report?

• free -mh
• git config --global http.postBuffer
• git config --global core.packedGitLimit
• git config --global core.packedGitWindowSize

[ellistalley]

"free -mh"

	total	used	free	shared	buff/cache	available
Mem:	7.4Gi	512Mi	6.9Gi	3.4Mi	157Mi	6.9Gi
Swap:	2.0Gi	0B	2.0Gi

"git config --global http.postBuffer"
20g

"git config --global core.packedGitLimit"
(No output)

"git config --global core.packedGitWindowSize"
(No output)