FS#79236 - [podman] gvproxy missing from /usr/lib/podman

Attached to Project: Arch Linux
Opened by Violet (Violettica) - Saturday, 29 July 2023, 00:26 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To David Runge (dvzrv)
Morten Linderud (Foxboron)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The following error message appears when attempting to run `podman machine start` on a fresh install.

Error: unable to start host networking: "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."

This is due to the binary `gvproxy` being missing from /usr/lib/podman. Other helper binaries are there, but not gvproxy.

This resembles a similar issue that occurred on the brew repository: https://github.com/containers/podman/issues/12161

Additional info:
* package version: 4.6.0-1

Steps to reproduce:
1. Install podman fresh.
2. Run `podman machine init`
3. Run `podman machine start`
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:19 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/podman/issues/1
Comment by loqs (loqs) - Saturday, 29 July 2023, 18:01 GMT
gvisor-tap-vsock which contains gvproxy is currentily in AUR [1].
Edit:
The attached PKGBUILD updates gvisor-tap-vsock to 0.7.0. Is podman able to use it?

[1] https://aur.archlinux.org/packages/gvisor-tap-vsock
Comment by Toolybird (Toolybird) - Saturday, 29 July 2023, 21:19 GMT
Any particular reason you want to run `podman machine...' on Linux? According to the man page [1], its main use is on MacOS and Windows (for obvious reasons). Even though it's supported on Linux, most folks would naturally prefer to run Linux containers natively [2].

The container networking code uses "netavark" these days, but for some reason `podman machine...' still wants gvproxy...(which basically confirms nobody uses `podman machine...')

[1] https://man.archlinux.org/man/extra/podman/podman-machine.1.en
[2] https://github.com/containers/podman/issues/14809#issuecomment-1173985886
Comment by David Runge (dvzrv) - Wednesday, 30 August 2023, 07:43 GMT
@Violettica: Thanks for the ticket.

As pointed out by loqs I guess the way to go here would be to package gvisor-tap-vsock (which seems also useful for QEMU setups).
Have you tried building the provided PKGBUILD and running it with podman?

Loading...