@friism Hi, updates ?
Soft symlinks work fine when created through the Windows host machine (either through bash.exe or WSL) and show up correctly on containers/VMs, but symlinks created inside containers appear as text files on the Windows host machine. Why ? Any fix that will make Windows/WSL recognize those symlinks as pointers rather than text files ? If adding mfsymlinks option to SMB3 client, allows it to read symlinks correctly, there is no reason why Windows cannot interpret them as symlinks.
Symlinks created by Windows host machine (WSL/Bash.exe/cmd.exe)::
- • Windows (WSL or Cygwin Bash.exe) -
️ symlink works - • Docker container - ️ symlink works
- • Hyper-V VM - ️ symlink works
Symlinks created by Docker containers::
- • Windows (WSL or Cygwin Bash.exe) -
appears as a text file - • Docker container - ️ symlink works
- • Hyper-V VM - ️ symlink works only with SMB 3.0 &
mfsymlinksoption (Resources for hot to achieve that shared_folders_hypver-v_ubuntu_guest & other posts using Unix commandmount -o mfsymlinks,<....>docker-on-windows-cifs-v3-02-mounts-failing-with-big-file-count)
Its 2 years already, is there a solution for making containers symlinks compatible with Windows Subsystem for Linux or Cygwin Bash ?
Use case: I’m installing node_modules from both WSL side and Docker containers side. In WSL host machine, the container’s node_modules/.bin symlinks appear as text files rather than pointers.
This issue made me a lot of headaches, will switching to Linux host development setup remove the need for all these workaround ?
Docker Version
- Windows 10 Pro 1803, OS build 17134.345, Developer mode turned on.
- WSL Debian GNU/Linux 9.5 (stretch)
- Docker for Windows 2.0.0.0-beta1-win75 (19925) edge 915f68b
- MobyLinuxVM kernel 4.9.125-linuxkit
- Docker Engine : 18.09.0-ce-beta1
- Container - any Linux container.
- Hyper-V VM Ubuntu 18.04.1