Cant share drive if windows account doesnt have password

[kripergvg]

Expected behavior

If a local windows account does not have password then a password should not be required

Actual behavior

The password textbox required regardless windows account settings

Information

Steps to reproduce the behavior

1. Create the local admin account without password
2. Try to share drives

[friism]

This is a wont-fix since allowing drive-sharing on accounts with no windows password would not be safe.

[G-Rath]

@friism How it is more secure to give docker the password to my account, than to not have a password in the first place?

Docker requires you to give it your password. Meaning that the password itself doesn't actually matter; it's all about the access. It doesn't matter if the password is 100 characters, or 0, so long as Docker can access the files.

It's my choice if I want a password or not. You shouldn't be trying to force security policies on me that I don't want.

So now, when using docker I have two choices:

• Add a password to my account (thus forcing a security policy that I don't agree with nor want on my personal computer)
• Create a new local user account (thus littering my personal computer with files for a user account that I don't want, along with requiring me to either give the account a very easy password which makes it very insecure anyway, OR give it a complex password, that - based on the some of the issues I've seen - I'll be required to re-enter for docker anyway on a regular basis).

I don't want to do either of these things. I know the risks of not having a password on my account - it's why I don't have one and still sleep at night.

But because I have to have one for docker, I'll be actively looking to stay as far away from docker as possible, until such time that they stop attempting to force security policies that don't affect them. (Sadly my work is looking to use them, meaning I'll likely be spending my time using the vagrant version).

I'm happy if you force me to watch a 15-minute video on password security, and click through 50 popups that chastise me for not having a password everytime I run a docker command, if it means I can use docker without having a password on my account.

[friism]

@G-Rath the way that Docker for Windows volume mounting works is that your entire c-drive is exposed as a network share. The Linux VM that runs Linux containers as part of Docker for Windows then mounts (using Samba) your whole c-drive inside the Linux VM so that linux containers running there can access your c-drive.

As part of the setup, Docker for Windows will create the share network share for the drive (if it's not already there). It would be incredibly unsafe and irresponsible for Docker for Windows to do that if your local user has no password, since Docker for Windows creating that share would make your drives mountable (with no password required) by anyone on your local network.

[G-Rath]

@friism That still doesn't change the fact that it's my choice. We're not babies - Inform us of the risk (which you should do anyway, password or no), and let us make the choice.

If you're worried about inexperienced developers, then make us jump thought several checkboxes and/or display warnings at every possible chance (like what pretty much every other developer cli, package manager, and application does).

Three more points:

• As strong as a password is, on Windows it can be easily brute forced (I tried at least 20 passwords the first time, with no rejection by Windows) - it's by far one of the more insecure methods of security.
• You don't know if my c-drive isn't already exposed as a network share.
• Why do I have to share my entire c-drive? Docker doesn't let me select a section of my c-drive, instead opting to require I share the whole thing.

At the end of the day, it should come down to that if that's what I want to do, I should be able to do it, given what I'm asking is for you to just accept a blank input field.

[G-Rath]

@friism Why is it not possible for Docker to use a private local network, solely between the physical computer and Linux VM? (Correct me if I'm wrong, but I thought that VirtualBox does this, or something similar).

Secondly, since it's apparently because of requiring Linux to use containers, would Windows containers in any way provide a possible solution to this problem?

[friism]

If you just want to run Docker Windows containers, you can run the Docker engine directly on Windows 10: https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/configure-docker-daemon#manual-installation

[G-Rath]

@friism I'm wanting to use docker for development, as that's what my workplace are switching to, and quite rightly - it's a very cool and powerful bit of tech.

Currently I seem to have three options for running docker:

1. Run it using a Vagrant passthrough

   • Pros: I don't have to create a new user account, or add a password to my existing account
   • Cons: Has some performance issues, since it's not running 'natively'.

2. Use Docker for Windows

   • Pros: Nice performance, since it's running 'natively' (or more so than 1.).
   • Cons: I have to create a new user account, or add a password to my existing account

3. Use Windows Containers

   • Pros: Nice performance (like with 2.), without having to create a new user account or add a password to my existing account
   • Cons: None!

From what I'm gathering, it seems that 3. will give me the best of both worlds?
Forgive me if I'm asking a naive question, but could you confirm for me if the part in italics for the pros of 3. is correct?

I'm reluctant to jump down what seems like it could be a very painful and annoying rabbit hole, only to encounter the whole issue all over again where I'm required to provide a password or create a new user account.

[friism]

Note that with just raw Docker Windows containers, you cannot (yet) run Linux containers (although that's being worked on).

You can also use Toolbox: https://docs.docker.com/toolbox/toolbox_install_windows/

This is similar to your option 1, but Toolbox automates setup and upgrade of the VirtualBox VM

[LongLiveCHIEF]

This is completely ignorant of the current security landscape. Two factor and/or Authentication agent methods of administrative authentication for windows are now the norm.

Most admin accounts these days don't have passwords, not because it's less secure, but because they're using some sort of Authentication provider that requires credential entry for any privileged access. (Smart Card or 2FA token).

This makes it literally impossible for the docker daemon to start.

Please re-open.

[mikaheikkinen]

Its impossible for me to use docker for windows because smarcard is not supported as authentication method when trying to share volume between host and container. We don't have password. Please fix this.

[dtvn]

@G-Rath the way that Docker for Windows volume mounting works is that your entire c-drive is exposed as a network share. The Linux VM that runs Linux containers as part of Docker for Windows then mounts (using Samba) your whole c-drive inside the Linux VM so that linux containers running there can access your c-drive.

As part of the setup, Docker for Windows will create the share network share for the drive (if it's not already there). It would be incredibly unsafe and irresponsible for Docker for Windows to do that if your local user has no password, since Docker for Windows creating that share would make your drives mountable (with no password required) by anyone on your local network.

@friism If you have this much time, why don't you stick this problem to your roadmap. Seriously, admit it, you're lazy that you don't wanna fix it, don't you?

(This is what users got for using some popular thing.)