It is very inconvenient because a mount like "/ tmp / docker-desktop / shadowing-mounts / qwertyu123456xxxxxx / mnt / c / Users /" occurs. For some reason, there is no problem when opening the default Linux application, so I can guess that something is wrong with the Windows terminal or the Docker Desktop side ...?
[Search with " shadowing-mounts "for the time being](https://www.google.com/search?q=%22shadowing-mounts%22&safe=active&sxsrf=ALeKk01wN1nZ4qPdahP3EEuo7AYPqCNl_Q:1598685535914&source=lnt&tbs=qdr=lnt&tbs=qdr 1536 & bih = 760) and the following page will appear.
At present, there are many parts where the reproducibility is unclear, and there seems to be no official answer as to what to do. (Reference: 2020/08/29)
It seems that one of the methods reported to be solved for the time being is ** "restart WSL" **. Note that this is separate from restarting the OS itself. I also stopped the Linux Subsystem and restarted it, and it was restored (but I'm sure I'll get the same symptoms soon).
Follow the procedure below to stop and restart WSL alone.
cmd.exe
1. > net stop LxssManager #Stop
2. > net start LxssManager #Start-up
This should restore the mount directory once. If not, I think it's best to wait for an official answer. (If you can clarify the cause and report the reproducibility, go to Issue on Github ~~)
-[Windows 10] Necessity of starting LxssManager service | Improving the performance and security of personal computers -ASCII.jp: Starting Windows Subsystem for Linux and background tasks
Recommended Posts