-
Notifications
You must be signed in to change notification settings - Fork 291
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
Windows 10: Docker for Windows: unable to share drive #2549
Comments
I've never once managed to get the Windows drive sharing working on win10. I've tried all the community suggested workarounds over the last year (pre-sharing the drive, creating new users and giving them access, restarting services, rebooting etc.) on multiple different machines. As far as I can tell, volume sharing simply isn't available on windows 10. |
This certainly seems to be the case. I've had the same issue and no resolution in the previous issue. It needs another look at. |
yay! waiting since 2 years that Docker for Windows works properly. |
After update the docker for windows to latest version(Docker version 18.06.1-ce, build e68fc7a). I have the same issue. when I want to share C disk, a window came out. ask for password. I can't use my windows account to deal with it. what kind of account and password is required? Anyone who have the same issue, Please follow this way: Settings→Reset→Reset to factory default |
+1, same issue here, the workaround of creating a new account didn't work. I'm really trying to work on a Windows box, but it's hard. This is the type of thing that annoys, no error, no log, no solution simply doesn't work, and this with a simple feature of mount a persistent volume. |
same problem, try every workaround i can find, still not work. docker and windows 10 all newest build |
@mak003 I did a factory reset, and it worked! Hoping it might help to fix issue, here's my situation:
|
did every suggested workarounds (includ. the factory reset, create a new user, uninstall and reinstall ...) but it still didn't work for me |
Still not working :C |
I encountered a similar issues this morning running Docker Desktop Community on my Windows 10 Pro. I am currently running Docker Desktop CE
|
+1 Just out of the blue encountered the same issue as @nngo with the same versions. But I haven't been able to share my Edit: Reseting to factory defaults worked for me. |
Making sure this issue is getting the attention it needs :
It has been ages since I'm trying to fix it, but no luck ... |
To understand what's going on we need to have a look at the logs after the drive sharing failure has happened. If you can reproduce the problem, it would be really helpful if you:
Thanks for your help! |
I'm having the same issue. Attached is the log from when I try to share the drive.
|
Rentered my changed windows password after "reset to factory defualuts" solved my problem. |
I think the problem was related to the way windows deal with virtual networks, just a guess, I'm not sure. The point is that after reset/reinstall windows :( things worked. |
Are you on Windows 10 Enterprise ? |
Yeah, I think my firm blocks some stuff using the group policy, even if firewall rules don't. |
Yup, had to do the same to make things work. |
I had the same log message as @hallen93. It looks like special characters in the computer/domain or user name (like "ü" in my case) are not encoded correctly. After renaming my computer to English characters only, it worked even without prompting me for the password. |
"Reset to factory defaults" resolved this issue for me |
I had this issue for the first time here, diagnostic ID: from the logs
Reset to factory defaults does fix but also wipes out all the images that you might have. |
No answer if unset password in windows10 pro |
It works with me after clicking in I think the issue was changing user password. |
Enabling Smb protocol fixed it for me. (run Set-SmbServerConfiguration -EnableSMB2Protocol $true in Powershell) |
Using Windows 10 Enterprise Edition ? |
I reset to factory defaults before share my drive D: Running this command in a supervisord PowerShell Set-NetConnectionProfile -interfacealias "vEthernet (DockerNAT)" -NetworkCategory Public Then, I shared my drive D and you run the command again: Done! Now the sharing is able to see the host folder |
In my case the workaround was to make a local user, and use those credentials to share my drive. My main user is from an active directory domain, which I'm guessing is not supported. Many logs follow... A failed login with my domain account:
Here is the successful login with the local account:
In the windows event viewer (eventvwr.msc) during the failed login, I see this:
And if there are questions, I did reset docker-for-windows and restart my machine, before trying a second user. The login failure event is not appearing in the docker UI, so there's one issue there. The failure itself may be caused by that missing security ID. But that's guesswork, so just leaving this here in case it helps someone. |
All these didn't work:
The only solution was to create a new local account with
|
This worked for me on Windows 10 Pro: |
Also stopped working after upgrade my account to AD. This article helped: https://tomssl.com/2018/01/11/sharing-your-c-drive-with-docker-for-windows-when-using-azure-active-directory-azuread-aad/ |
I guess it's better to raise server on linux rather to mess up with win10. Idk why LinuxOnWindows is needed, to EEE? (because docker won't installs without headacke. I actually don't even bother to install docker via LoW. low chance it would work) |
If your firewall is configured to allow traffic on the Hyper-V network, and your drive is shared in "Shared Drives", this does work. There are lots of layers in Windows networking, as with ogres and onions. But with patience, it can be coaxed into working. I didn't have to add users, but I did move the data I wanted to share into the Public user space. |
Just the fact that the firewall config may break Docker volumes in Windows is a no-go IMHO for corporate environments where networking responsibilities/policies may be very de-coupled from the developers requirements, or even conflicting. That is the good thing of the VBox docker-machine approach, it brings its own shared volumes driver, no coupling with unrelated networking policies. |
This solution worked for me! Thanks! |
Hello, I found that adding your local user to Remote Desktop User group do the trick for me no need admin permission. Best |
I had the same issue with my AD account after changing the password so I did a "Reset to factory default" and was able to re-share my C drive with my AD account again. |
This is fixed with the new filesharing implementation in 2.2.0.3, so closing this ticket. |
Thank you very much @mak003, your tip worked well for me! |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Opening new issue because #690 is being ignored.
#690
The text was updated successfully, but these errors were encountered: