title: How to handle git under wsl2 network drive
body: <p>I just configured docker to run under wsl2. That worked without any relevant problems and our projects are running fine.</p>
  
  <p>I followed this article by docker on how to setup the wsl2 docker environment: <a href="https://www.docker.com/blog/docker-desktop-wsl-2-best-practices/" rel="nofollow noreferrer">https://www.docker.com/blog/docker-desktop-wsl-2-best-practices/</a></p>
  
  <p>The article recommends to put the project files into the linux system and NOT access it by using the mounts under <code>/mnt</code> for performance reasons.</p>
  
  <p>For accessing the files, the article suggests the following options:</p>
  
  <ul>
  <li>Use Visual Studio Code (which can access wsl directly)</li>
  <li>Use the network share under <code>\\wsl$\</code></li>
  <li>Run the IDE directly inside the linux</li>
  </ul>
  
  <p>Some collegues use IDE's that are neither compatible with linux nor can access wsl. So I tried to let them access the project through the network share. Those collegues use the git integration in their IDE's and are not comfortable with the git cli.</p>
  
  <p>Git works well, with just a little problem. We have files in the repository, that have the executable permission (+x). Thoses file have the perms 755 on linux and 644 on windows network drive.</p>
  
  <p>Because the actual file perms differ from the linux environment, git detects a change for those files.</p>
  
  <p>Is there a way, to expose the correct file perms to the windows environment?</p>
  
  <p>Do you have any other ideas on how to solve the problem?</p>