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

Shared Drives not applying #78

Closed
MadLittleMods opened this Issue Sep 14, 2016 · 7 comments

Comments

Projects
None yet
5 participants
@MadLittleMods

MadLittleMods commented Sep 14, 2016

Expected behavior

Entering correct credentials in the Windows Security dialog after sharing a drive will successfully share the drive with containers

Actual behavior

When sharing a drive, entering correct credentials re-opens the Windows Security dialog with no perceivable action taken.

Information

It looks like action might be taken and the drive is shared but it is unclear from the UI. Here is a snippet of the diagnostic log

[20:43:50.458][Auth           ][Info   ] Storing credentials: mlm:***
[20:43:50.468][NamedPipeClient][Info   ] Sending TryShare(C, mlm:***)...
[20:43:50.470][NamedPipeServer][Info   ] TryShare(C, mlm:***)
[20:43:50.491][Cmd            ][Info   ] Share name        C
[20:43:50.494][Cmd            ][Info   ] Path              C:\
[20:43:50.496][Cmd            ][Info   ] Remark            
[20:43:50.498][Cmd            ][Info   ] Maximum users     No limit
[20:43:50.500][Cmd            ][Info   ] Users             
[20:43:50.502][Cmd            ][Info   ] Caching           Caching disabled
[20:43:50.504][Cmd            ][Info   ] Permission        some-pc\MLM, FULL
[20:43:50.506][Cmd            ][Info   ] 
[20:43:50.508][Cmd            ][Info   ] The command completed successfully.
[20:43:50.511][Cmd            ][Info   ] 
[20:43:50.513][SambaShare     ][Info   ] "C" is shared
[20:43:50.515][SambaShare     ][Info   ] Challenging credentials with host

Steps to reproduce the behavior

  1. Open the Docker for Windows Settings
  2. Go to the "Shared Drives" tab
  3. Check the "C" drive and Press "Apply"
  4. Enter the credentials for your admin account in the Windows Security dialog and press "OK"
  5. Note the Windows Security dialog popping up again. Entering in credentials again just pops it again.
  6. If you just exit the Windows Security dialog, the "C" drive isn't checked

It looks like the Hyper-V driver machines can't mount volumes so I was looking into this option, moby/moby#22981 (comment)

@dgageot

This comment has been minimized.

dgageot commented Sep 14, 2016

Hi @MadLittleMods, thanks for the detailed report! Could you give a try to the Beta channel instead of the Stable channel? It contains multiple fixes to the file sharing.

@MadLittleMods

This comment has been minimized.

MadLittleMods commented Sep 14, 2016

@dgageot Same issue with Docker 1.12.1-beta25 (build:6833) 158f2ee

@friism

This comment has been minimized.

friism commented Sep 14, 2016

@MadLittleMods could you please upload a diagnostic dump (it's in the Docker tray icon menu) so we can get more info about your system?

@MadLittleMods

This comment has been minimized.

MadLittleMods commented Sep 16, 2016

Sorry @friism, I moved on to Docker Toolbox and VirtualBox driver. I would need to reinstall Docker for Windows and do the Hyper-V dance again.

@dgageot

This comment has been minimized.

dgageot commented Sep 16, 2016

@MadLittleMods I'm afraid I will have to close this issue as "Could not reproduce" then. Next version of Docker for Windows will have an improved file sharing that should solve similar issues. Feel free to reopen this ticket if you come back to using Docker for Windows!

@dgageot dgageot closed this Sep 16, 2016

@mattkrebs

This comment has been minimized.

mattkrebs commented Apr 6, 2018

A little more information on this, Having the same issue. I am running windows 10 pro on Parallels. My user on the Parallels VM which has admin rights is what I use when i enter credentials. After entering, the dialog closes and check box is unchecked. However if i create an new user for the VM at the Machine level not Company level, it works fine. however i would prefer to use the machine with my domain account.

Thanks

@markusschaber

This comment has been minimized.

markusschaber commented Jul 4, 2018

I also have a domain account, same symptoms (Windows 10). So maybe the problem is domain account vs local account?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment