Inconsistencies in Hyper-V podman machine commands #27723
Description
When a user on a Windows machine is not a member of the Hyper-V admins he cannot start/stop Hyper-V machines. But there are some other commands, that the user would technically be ablto to run, that we are currently blocking:
We block some commands that the user would be able to run
Commands like machine cp, machine ssh etc..., against an hyperv machine, should work too, even if the user doesn't have Hyper-V admin privileges.
When CONTAINERS_MACHINE_PROVIDER="hyperv", the user cannot manage a WSL machine
Inspecting or starting a wsl machine, if the default provider is hyperv, fails:
> $env:CONTAINERS_MACHINE_PROVIDER="hyperv"
> podman.exe machine inspect mywslmachine`
Error: Hyper-V machines require Hyper-V admin rights...
> podman.exe machine start mywslmachine`
Error: Hyper-V machines require Hyper-V admin rights...And this is awkward because podman machine ls works and lists the WSL machines.