Opened 3 years ago

Closed 3 years ago

#63628 closed defect (fixed)

podman @3.4.0_0: doesn't look for gvproxy in the MacPorts location

Reported by: jre21 (Jacob Emmert-Aronson) Owned by: judaew (Vadym-Valdis Yudaiev)
Priority: Normal Milestone:
Component: ports Version: 2.7.1
Keywords: Cc:
Port: podman

Description

On upgrading podman to 3.4.0_0, podman machine start immediately started erroring out with the following message:

Error: unable to start host networking: "could not find \"gvproxy\" in one of [/usr/local/opt/podman/libexec /opt/homebrew/bin /opt/homebrew/opt/podman/libexec /usr/local/bin /usr/local/libexec/podman /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman]"

I resolved this by setting the configuration value described in ​https://github.com/containers/podman/issues/11960#issuecomment-943079955, but the port should ship this in a default config file so that users don't have to discover and correct this error manually.

Change History (2)

comment:1 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)

Thanks for the ticket. I will overwrite the default directory listing for defaultHelperBinariesDir at compile time. This fixes the problem.

comment:2 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)

Resolution: → fixed
Status: assigned → closed

In 61fe5542908da7e0ba47357ca12f92074c3175dd/macports-ports (master):

podman: Overwrite dir list in defaultHelperBinariesDir

See: ​https://github.com/containers/podman/issues/11960
Closed: #63628

Note: See TracTickets for help on using tickets.