Re: [EXTERNAL] Re: Git clone failure
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Sep 25, 2024, 21:00 UTC
- Message-ID
- <ZvR58tnLEMBZC4fa@tapette.crustytoothpaste.net>
- In-Reply-To
- <SI2P153MB07185B9AED66870BBAD3C78AD4692@SI2P153MB0718.APCP153.PROD.OUTLOOK.COM>
On 2024-09-25 at 08:49:11, Krishna Vivek Vitta wrote:
Show 15 quoted lines
> > Hi Brian > > Thanks for the response. > > It is a WSL2 environment with kernel version: 5.15.153. We have used a kernel version 6.6.36.3 as well. Scenario fails there as well. > > root@DESKTOP-OOHD5UG:/sys/kernel/debug/tracing# uname -a Linux DESKTOP-OOHD5UG 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux > > Mount point information: > C:\ on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=5,wfd=5) > > We aren't using any sort of file syncing service. > > We have installed a defender software which is marking mount points for FANOTIFY to intercept filesystem events. On removing the marking, git clone succeeds.
My guess is that whatever software you're using to intercept file system events is causing the "unknown error occurred while reading the configuration files" message and you should remove that software and reboot to see if the problem goes away, even though fanotify is enabled.
It's very common that the kind of "defender software" you're using breaks a variety of software, including Git and Git LFS, and in general, the recommendation we give in the Git FAQ is that you use only the system default antivirus (and on Linux or WSL, none, since there is no default).
-- brian m. carlson (they/them or he/him) Toronto, Ontario, CA