-
Notifications
You must be signed in to change notification settings - Fork 2k
can't create machine as a user that has "Hyper-V Administration" rights #2989
Comments
I've managed to get this working locally (see peschkaj@3480af2) but VM creation fails after the security checks pass:
Base VHDs are successfully created, but it looks like the VM isn't correctly being registered with Hyper-V. I can't see it using |
Spoke too soon - after some good old fashioned |
possibly due to the permissions on the folder where you are creating your VMs? |
I added myself to the Hyper-V Administrators local group, which should be enough permissions and that didn't work. I then gave Hyper-V Administrators full control of the base folder (G:\docker) and gave it cascading permissions. That also didn't work. The appropriate directories and files are being created when run as my user, but only the I recreated the docker folder as
Even after doing this, the
On a lark, I gave my user account full control and that also failed. I ran the PowerShell command that |
using @peschkaj change as a base I was able to get this working. It is only the |
For using an SID as parameter - which is better because of potential i18n issue with role name - "isInRole()" expect a "System.Security.Principal.SecurityIdentifier" object instead of a "String". That's because of this error that isHypervAdministrator() always return false and and consequently "Administrator" role is requested.
For using an SID as parameter - which is better because of potential i18n issue with role name - "isInRole()" expect a "System.Security.Principal.SecurityIdentifier" object instead of a "String". That's because of this error that isHypervAdministrator() always return false and and consequently "Administrator" role is requested. Signed-off-by: Olivier Bourgeat <olivier.bourgeat@laposte.net>
using
docker-machine create --driver hyperv
should not require administrator rights.Users who are a member of "Hyper-V Administrators" groups can create/destroy Virtual machines.
This is the offending code - the check should check the user is an administrator or a member of "Hyper-V administrators"
see this artical for the old gory details for old OSes that are no longer needed with Windows 8+ Server 2012 R2+...
The text was updated successfully, but these errors were encountered: