Replies: 1 comment
-
Ok, I must have mistyped the environment variable to enable the HyperV provider. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm playing around podman on windows, and I wanted to test the new HyperV support.
With the latest Podman Desktop release (1.10.2) I could create a new VM but only with the command line.
and I never managed to make the Podman UI shows the images or the container running in the VM :/
Then on another computer I install the latest podman setup for windows. and I could not create an HyperV VM with it...
Did I missed something ?
Is it only supported with podman desktop ?
I'm a bit lost, here.
And then as a side question when, how is the named pipe \.\pipe\docker_engine configured ?
is there support to change the permission on it ? (I found some powershell script to adapt the permission, but wanted to know if it is something in the roadmap. I think docker desktop allow to assign a special group to access the named pipe...)
Thanks for any hint or pointer.
Beta Was this translation helpful? Give feedback.
All reactions