Docker Community Forums

Share and learn in the Docker community.

Symlinks on shared volumes not supported


(Noobydp) #41

Not sure if this helps, but instead of using a symlink I added a mount point for a separate drive I want to use under %Userprofile%\Docker using the Disk Management console. Docker seemed to be happy using these folders.

1 Open Disk Management Console
2 Right click on partition / drive you want to use for docker content
3 Click Change Drive Letter and Paths
4 Click Add
5 Select “Mount in the following empty NTFS folder”, and click Browse
6 Navigate to your user folder and select / create a folder to mount under
7 Click OK OK

You can now use this folder which is mapped to the separate partition


(Ndipiazza) #42

Verified here on windows 10 professional we are definitely all Fixed. Now able to do all sorts of amazing things with Windows + Docker + Linux containers where i share a file system with windows. Excellent work!!!


(Skalex) #43

Hi! I’m experiencing this problem with Docker ToolBox under Windows 7. Any ideas if it’s considered to be fixed? Related issues are already closed.

anyway, I’ll try other options as some mentioned, like running mklink /d from windows.

Thanks!! byee

The error is
symlink(): Read-only file system

And my current environment details:
Win 7 Ultimate SP 1

$ docker version
Client:
Version: 17.10.0-ce
API version: 1.33
Go version: go1.8.3
Git commit: f4ffd25
Built: Tue Oct 17 19:00:02 2017
OS/Arch: windows/amd64

Server:
Version: 17.11.0-ce
API version: 1.34 (minimum version 1.12)
Go version: go1.8.5
Git commit: 1caf76c
Built: Mon Nov 20 18:39:28 2017
OS/Arch: linux/amd64
Experimental: false

VirtualBox 5.2.0 r 118431

Edit: Running mklink /d from outside the container works. I ran it from the windows command line and with administrative privileges


(Strarsis) #44

I had success using the handy Link Shell Extension tool and using ‘Junction’ as link type.

In case you are using this for developping on a WordPress plugin which original directory is outside the WordPress site: Be aware that composer could nuke the plugin directory and also the original plugin directory when you manage your plugin/themes using composer (e.g. roots Bedrock installation).


(Myuserindocker) #45

@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) - :heavy_check_mark:️ symlink works
  • • Docker container - :heavy_check_mark:️ symlink works
  • • Hyper-V VM - :heavy_check_mark:️ symlink works

Symlinks created by Docker containers::


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