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
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

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).