podman
podman copied to clipboard
Simplifying installation and use of Podman for non admin users on Windows
Feature request description
There are different cases when podman requires elevated mode on Windows:
- the installer copies files in
C:/Program Files - the installer checks if WSL and HyperV are installed
- on Hyper-V, every execution of
podman machine initcreates HKLM registry keys - on Hyper-V, every execution of
podman machine start/stop/reset...requires the privileges to control a Hyper-V VM - the first execution of
podman machine initinstalls Hyper-V or WSL if they are not installed yet
Suggest a potential solution
Here is a list of proposals to address or simplify the points above:
- the installer should copy files under the current user
%HOME% - the installer should not detect WSL and HyperV (
machine initshould be responsible for it and for consequential actions) podman machine initshould re-execute itself in elevated mode and create the HKLM reg key only once (nextmachine initwill reuse the key)- current user has to be the administrator or part of the Hyper-V administrators. At first execution, if the condition isn't met, the
podman machinecommand re-executes itself in elevated mode to add the user to the Hyper-V administrators group podman machine initshould re-execute itself in elevated mode and install the Windows component (this was the 4.x behavior that is currently broken)
Additional context
Related issues:
- #22101
- #22994
- #23000
- #23578
- #25037
- #25038
- #25523