Can't create HyperV podman machine although being part of HyperV admin group
Issue Description
Tried podman machine init with CONTAINERS_MACHINE_PROVIDER=hyperv and got:
Looking up Podman Machine image at quay.io/podman/machine-os:5.0 to create VM
Getting image source signatures
Copying blob 4918dae5ef6d done |
Copying config 44136fa355 done |
Writing manifest to image destination
4918dae5ef6d941322860602899cc4d12ba4e086860527a231b1ae21bb4110c2
Extracting compressed file: podman-machine-default-amd64.vhdx: done
time="2024-03-20T19:38:54+01:00" level=error msg="Descripteur non valide"
Error: Accès refusé.
I am a member of the HyperV admin group:
Steps to reproduce the issue
Steps to reproduce the issue
- set CONTAINERS_MACHINE_PROVIDER=hyperv
- podman machine init
Describe the results you received
Looking up Podman Machine image at quay.io/podman/machine-os:5.0 to create VM
Getting image source signatures
Copying blob 4918dae5ef6d done |
Copying config 44136fa355 done |
Writing manifest to image destination
4918dae5ef6d941322860602899cc4d12ba4e086860527a231b1ae21bb4110c2
Extracting compressed file: podman-machine-default-amd64.vhdx: done
time="2024-03-20T19:38:54+01:00" level=error msg="Descripteur non valide"
Error: Accès refusé.
Describe the results you expected
machine should be created
podman info output
Win11Pro
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
@n1hility does this make you think that something we did in libhvee is actually requiring admin?
the admin is requirement for the hvsock. looking at possible ways to deal with this.
#22161 will require admin now ... perhaps for 5.1 we can work around the hvsock requirement. we have a number of ideas.
A friendly reminder that this issue had no activity for 30 days.