Open bismip opened 1 month ago
hyperv does not technically require admin but the use of the registry keys to create the vsock does.
would people rather have a priv elevation for podman machine init
?
hyperv does not technically require admin but the use of the registry keys to create the vsock does.
It should still work for members of Hyper-V Administrators
, depending on how podman does it. I'll have a look at the code later.
would people rather have a priv elevation for
podman machine init
?
If admin is a requirement, this is probably the preferred way in restricted enterprise environments.
It should still work for members of
Hyper-V Administrators
, depending on how podman does it. I'll have a look at the code later.
When I tested this last time, this was not true. The hvsock registry entries required admin.
A friendly reminder that this issue had no activity for 30 days.
Issue Description
Podman checks for admin permissions when running with Hyper-V on Windows. Members of the group
Hyper-V Administrators
should be able to manage VMs without admin permissions.Steps to reproduce the issue
Run
podman machine init
without admin privileges.Describe the results you received
Error about missing permissions.
Describe the results you expected
It should work.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
No
Additional environment details
Windows 11
Additional information
No response