Dev build of podman 4.2.0 (win) doesn't install for me

[n1hility]

podman 4.2.0-dev doesn't install for me

Originally posted by @rorygilfillan-absa in #14593 (comment)

[n1hility]

@ericis wrote:

@n1hility I got the same error. I ran the standard Windows "Unblock", since it was initially blocked from even running because it was "not trusted" (signed).

Steps:

1. Downloaded
2. Run (blocked because of Windows trust issue on unsigned software from the internet)
3. Reviewed your repo and changes 👍🏻
4. Unblock
5. Run again
6. Accept prompt for escalated privileges (expected)
7. Installation begins, but results in the error @rorygilfillan-absa shared above

Windows 10 Enterprise

[n1hility]

@ericis Thanks for trying! Just to confirm the 4.1.x msi does not have this issue for you?

Do you have any other virus scanning software that might have blocked one of the actions? There is an executable installed which is ran to update the path, and if something prevents that from running you would see that.

Could you try to capture logging and past the output to a gist/pastebin to see if any additional details are revealed:

msiexec /i podman-v4.2.0-dev.msi /l*v installpodman.txt

Thanks!

[ericis]

Let me know if you'd like me to retest anything @n1hility

[n1hility]

@ericis hey eric, sorry for the long delay. I have an early build of a new signed installer if you would like to give that a spin:
https://github.com/n1hility/podman-builds/blob/main/podman-4.2.0-unofficial-setup.exe

[ericis]

Will do. I'll reply by end of day (US EST)

[ericis]

Apologies for the delayed response @n1hility . This installer didn't quite work in the end, but installed successfully...

• Installed successfully

• podman machine init success

  • Fedora download
  • Fedora installation and configuration

• podman machine start

  Starting machine "podman-machine-default"
  
  This machine is currently configured in rootless mode. If your containers
  require root permissions (e.g. ports < 1024), or if you run into compatibility
  issues with non-podman clients, you can switch using the following command:
  
          podman machine set --rootful
  
  API forwarding listening on: npipe:////./pipe/docker_engine
  
  Docker API clients default to this address. You do not need to set DOCKER_HOST.
  Machine "podman-machine-default" started successfully
  

• podman images

  podman images
  Error: error creating host key callback function for C:\Users\[USER_NAME]\.ssh\known_hosts: open C:\Users\[USER_NAME]\.ssh\known_hosts: The system cannot find the file specified.
  

[n1hility]

@ericis thanks for sharing and testing ! I am glad that the installation portion worked for you. Sorry about the ssh errors, this build was produced from the lastet main build tree, which was partway through an unrelated ssh refactor. The 4.3 release will complete the refactor and not have this issue. As a a workaround you can create an empty known_hosts file if you want to try it out.