F41?: gvproxy not found when running podman machine

[tulilirockz]

I dont know if this is a F41-only problem but I dont seem to be able to start up a podman machine on Bluefin right now. This does look a ton like an upstream issue but I havent tested anything yet

~> podman machine start amogus
Starting machine "amogus"                                                                                                                                              
Error: could not find "gvproxy" in one of [/usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/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.

[tulilirockz]

Layering gvisor-tap-vsock adds gvproxy to /usr/libexec/podman. But it also requires virtiofsd to be in $PATH, probably symlinking it from /usr/libexec/virtiofsd to /usr/bin could be cool? Idk honestly

[bsherman]

I did some digging, and I think the best solution is to install the package podman-machine.

(see: containers/podman#23127 )

I think it quite reasonable to add this package to Bluefin (and ucore, actually) as it will make podman machine work as expected...

The podman-machine will pull in gvisor-tap-vsoc and resolves both issues of a missing gvproxy and virtiofsd.

@tulilirockz do you want to update your PR #1861 to only add this package? I believe it should be added to all not just dx. And of course, then we don't need the symlink in workarounds.

[tulilirockz]

@bsherman Fixed the PR on my phone so I had to add some commits reverting the changes and adding podman-machine. Now it should be good to go!

[bsherman]

Correction to my comment above... probably I won't add this to ucore unless it's to ucore-hci since it pulls in all of qemu, and that would add more to the weight of ucore that is appropriate.