Cannot clone WSL2-Linux-Kernel

[jibnew]

Windows Version

Microsoft Windows [Version 10.0.22631.4602]

WSL Version

2.3.26.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.167.4

Distro Version

Ubuntu 24.04

Other Software

I tried (from within wsl) git clone https://github.com/microsoft/WSL2-Linux-Kernel.git --depth=1 -b linux-msft-wsl-6.6.y three times, it keeps failing after a while, with the message

git clone https://github.com/microsoft/WSL2-Linux-Kernel.git --depth=1 -b linux-msft-wsl-6.6.y
Cloning into 'WSL2-Linux-Kernel'...
remote: Enumerating objects: 86697, done.
remote: Counting objects: 100% (86697/86697), done.
remote: Compressing objects: 100% (80163/80163), done.
error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
error: 3858 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

Last time it happened at around 98% completed.
What do I do? Just try again and again?

Repro Steps

run wsl.exe
when in wsl, run git clone https://github.com/microsoft/WSL2-Linux-Kernel.git --depth=1 -b linux-msft-wsl-6.6.y
get

error: RPC failed; curl 92 HTTP/2 stream 5 was not closed cleanly: CANCEL (err 8)
error: 3858 bytes of body are still expected
fetch-pack: unexpected disconnect while reading sideband packet
fatal: early EOF
fatal: fetch-pack: invalid index-pack output

Expected Behavior

WSL2-Linux-Kernel must be cloned into the directory with the same name

Actual Behavior

Nothing is cloned anywhere

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• WSL2-Linux-Kernel repository mess (#7957), similarity score: 0.78
• Git failed (#9393), similarity score: 0.77
• Git can't clone when WSL1 is installed on Citrix (#10529), similarity score: 0.76
• git clone not working (#10615), similarity score: 0.75
• Git clone fails with Recv failure: Connection reset by peer (#10191), similarity score: 0.73

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[elsaco]

I did a quick test and the cloning worked w/out issues:

elsaco@texas:~/GitHub$ git clone https://github.com/microsoft/WSL2-Linux-Kernel.git --depth=1 -b linux-msft-wsl-6.6.y
Cloning into 'WSL2-Linux-Kernel'...
remote: Enumerating objects: 86697, done.
remote: Counting objects: 100% (86697/86697), done.
remote: Compressing objects: 100% (80167/80167), done.
remote: Total 86697 (delta 9273), reused 22037 (delta 5665), pack-reused 0 (from 0)
Receiving objects: 100% (86697/86697), 237.33 MiB | 8.31 MiB/s, done.
Resolving deltas: 100% (9273/9273), done.
Updating files: 100% (81819/81819), done.

WSL and git versions used for testing:

elsaco@texas:~/GitHub$ git --version
git version 2.43.0
elsaco@texas:~/GitHub$ wslinfo --wsl-version
2.4.8

Please check your WSL networking setup. Also, can you try cloning on Widows side and see how it works.

[sirredbeard]

I have seen this happen sporadically when cloning the kernel. Usually trying again picks up where the clone left off.

Are you on a VPN, wireless, or other connection that may be intermittent?

Are you cloning to the WSL filesystem or do a disk on /mnt/...?

[jibnew]

I have seen this happen sporadically when cloning the kernel. Usually trying again picks up where the clone left off.

Are you on a VPN, wireless, or other connection that may be intermittent?

Are you cloning to the WSL filesystem or do a disk on /mnt/...?

Wifi, no VPN, cloning to ~ in WSL. Actually one more attempt finally succeeded.