New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't access network drives (shared folders) #58
Comments
#46 ? Try setting |
Also maybe take this to upstream cygwin. This update to symlink code has caused issues here, but I don't think cygwin has released a version including those changes yet, so we're getting all the reports of the fallout. |
@jeremyd2019 Thanks for the super-fast response! 🚀 The
I am reluctant to do so because I don't really use cygwin.
I see. Pardon my ignorance but does this new symlink code improve performance or is it more of an architectural change? |
My understanding is that it fixed an issue in cmake's tests, but it also causes issues with mapped and subst drives, and possibly docker mount points? @github-cygwin |
This also causes issues with mapped volumes with docker containers with the same "too many levels of symbolic links" error.
Setting |
30089b3 is supposed to have fixed this. It would be interesting to see if it fixed the Docker issue too (it seems likely it did) |
Hi, I apologize if this is the wrong place to post this issue.
I recently installed MSYS2 on my Windows 10 VM in VirtualBox, and I quickly found out that I can't navigate to any of my shared folders (which are mounted as Network Drives in Windows). The primary error message is
Too many levels of symbolic links
.Here is some raw output from the shell:
Drive D is a CD-drive and I am able to access it normally, as well as the C drive (
/c
). All of my projects are on the host system so I need to access them via mechanisms such as shared folders, which are implemented as network drive mounts in VirtualBox's Windows guests.I am able to use
cmd
andpowershell
normally in network drives as well as many other programs, this is one of the rare occasions where they have caused me trouble, I don't even recall the last issue I had with them.The text was updated successfully, but these errors were encountered: