Skip to content
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

Unable to set "Share Drive" #4760

Closed
1 of 2 tasks
tariqg11 opened this issue Sep 19, 2019 · 4 comments
Closed
1 of 2 tasks

Unable to set "Share Drive" #4760

tariqg11 opened this issue Sep 19, 2019 · 4 comments

Comments

@tariqg11
Copy link

tariqg11 commented Sep 19, 2019

  • I have tried with the latest version of my channel (Stable or Edge)
  • I have uploaded Diagnostics
  • Diagnostics ID: BC639E78-575A-4201-AFC0-3CF4035D7769/20190919075044

Expected behavior

When click on 'Apply' in Settings after selecting to 'share' the "C" drive, the settings to take affect.

Actual behavior

When 'Apply' is clicked in Settings after selecting to 'share' the "C" drive the 'busy-circle' shows up and never goes away until the 'Docker Desktop' application is killed from Task Manager.

Information

  • Windows Version: Win 10 Pro
  • Docker Desktop Version: 2.1.0.3 (38240)
  • Are you running inside a virtualized Windows e.g. on a cloud server or on a mac VM: No

Steps to reproduce the behavior

  1. Right click on the Docker icon in tray, select settings
  2. Select "Shared Drives"
  3. Select the box under "Shared" column for "C"
  4. Click on "Apply" button at bottom right of the settings box and 'busy circle' shows up.
@mryserb
Copy link

mryserb commented Sep 19, 2019

Had a similar problem, on my machine the lanmanserver (described as "Server" in windows services) was deactivated/stopped... after enabling it, it worked!

@tariqg11
Copy link
Author

Had a similar problem, on my machine the lanmanserver (described as "Server" in windows services) was deactivated/stopped... after enabling it, it worked!

Thank you, I tried to enable it from TaskManager/Services first but turns out it was disabled, I had to do some digging and it was listed as "Server" in the Windows Administrative Toos > Services, once enabled from there then I was able to start the service from Task Manager / Services !!!!

Thank you !

@docker-robott
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

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.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Jul 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants