I’ve been having some issues with setting up devilbox after migrating to windows from debian.
On my linux system I had my projects stored in /home/www and symlinked into the devilbox data directory. After adding $HOME:$HOME volumes settings into docker-compose.override.yml it worked flawlessly.
Now, on windows I have a different setup (duh):
- My projects are located in: Y:\projects\project
- Devilbox is located in Y:\devilbox (data folder Y:\devilbox\data\www, so default)
- I’m using WSL and it’s set up so the windows disks mount in /, so /c /y etc. This translates the two locations above to /y/projects/project and /y/devilbox
- I’ve added volumes to the PHP container, so the /y directory is mapped to /y in the shell.
- I’ve added symlinks (in WSL): ln -s /y/projects/project/web /y/devilbox/data/www/project/htdocs
Now what happens, is that after checking in the container shell, the symlink /shared/httpd/project/htdocs is red (points to nowhere), even though the path /y/projects/project exists in the shell (due to volume mapping).
What I’ve tried is creating the symlink while in the container’s shell -> it does work, BUT it’s not stable. For some reason, the php script in my project cannot open the log file (located in /y/projects/project/var/logs/dev.log and yes, it’s there).
Any ideas on what might be the problem?
Just found about about this thread -> https://github.com/docker/for-win/issues/2005
That’s the same issue I’m having, looks totally docker related.