search

containers / podman-desktop-e2e

Podman desktop e2e tests
Apache License 2.0
3 stars 8 forks source link

Podman Machine HyperV start using admin rights errors with gvproxy missing #228

Open odockal opened 3 days ago

odockal commented 3 days ago 
Standard Error: podman : Getting image source signatures At C:\Users\rhqp\pd-e2e\tmp_script.ps1:10 char:9 +         podman machine init --rootful *>> "C:\Users\rhqp\pd-e2e\stdou ... +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (Getting image source signatures:String) [], RemoteException     + FullyQualifiedErrorId : NativeCommandError   Copying blob sha256:c5c70e9bc7729df7670dfc7f00e4bd2b25d344cde0216182bb71d9797c62255c Copying config sha256:44136fa355b3678a1146ad16f7e8649e94fb4fc21fe77e8310c060f61caaff8a Writing manifest to image destination
Starting HyperV Podman Machine ...
Standard Output: Starting machine "podman-machine-default"
Standard Error: podman : Error: could not find "gvproxy" in one of [C:\Program Files\RedHat\Podman].  To resolve this error, set the  helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries. At C:\Users\rhqp\pd-e2e\tmp_script.ps1:10 char:9 +         podman machine start *>> "C:\Users\rhqp\pd-e2e\stdout.txt" 2> ... +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : NotSpecified: (Error: could no...elper binaries.:String) [], RemoteException     + FullyQualifiedErrorId : NativeCommandError  
List HyperV Podman Machine ...
odockal commented 1 day ago

Workaround could be to place necessary binaries (gvproxy, etc.) into manually created C:\Program Files\RedHat\Podman folder. or set the helper_binaries_dir key in the [engine] section of containers.conf.

odockal commented 1 day ago

Another solution is to install podman from setup.exe which places the binaries on the right location.