Podman version 5.3.2 is brocken, probably because of gvproxy dependency

[janwesterkamp]

Output of brew config

brew config
HOMEBREW_VERSION: 4.4.17-33-g0a422da
ORIGIN: https://github.com/Homebrew/brew
HEAD: 0a422daf684d652d82d4894151af419740406d08
Last commit: 3 hours ago
Branch: master
Core tap HEAD: 26cd4ffdb8dd0d79d397ebd98f4ceb2d25dd614b
Core tap last commit: 3 hours ago
Core tap JSON: 23 Jan 11:22 UTC
Core cask tap HEAD: 0b37f1aa1a8af8b82c71d110994d418fd717447a
Core cask tap last commit: 3 hours ago
Core cask tap JSON: 23 Jan 11:22 UTC
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 16
HOMEBREW_SORBET_RUNTIME: set
Homebrew Ruby: 3.3.7 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/3.3.7/bin/ruby
CPU: 16-core 64-bit kabylake
Clang: 16.0.0 build 1600
Git: 2.39.5 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 8.7.1 => /usr/bin/curl
macOS: 14.7.2-x86_64
CLT: 16.2.0.0.1.1733547573
Xcode: 16.2

Output of brew doctor

brew doctor 
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  hyperkit
  terraform
  vault

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  aws-c-compression
  aws-c-http
  aws-c-mqtt
  aws-c-event-stream
  aws-c-common
  aws-c-io
  aws-checksums
  aws-c-cal

Description of issue

After updating to podman 5.3.2 it's not being able to start the podman machine, see error:

Error: unable to connect to "gvproxy" socket at "/var/folders/q5/4w6x1frx61g34vnyhzmm5zsr0000gn/T/podman/podman-machine-default-gvproxy.sock"

According to the (closed) issue on the podman repo this mght be because of an newer (!), problematic version of gvproxy being used in homebrew:

containers/podman#25103

This was part of the recent update to the formula:

Homebrew/homebrew-core@9261d2e

I reproduced the porblem by uninstalling/installing podman and podman-desktop, deleteing the podman machine multiple times and deleting the configuration to have a new created when installing again - with no success.

At the end, I followed the official documentation and installed the official packages from podman (using the podman-desktop variant, this still installs podman 5.3.1) and was able to start the podman machine without issues.
So this is a workaound, but I think it need to be fixed here to keep the homebrew option usable.

Update step was podman version 5.3.1_1 to 5.3.2.

Brew info output (before uninstalling):

brew info podman   
==> podman: stable 5.3.2 (bottled), HEAD
Tool for managing OCI containers and pods
https://podman.io/
Installed
/usr/local/Cellar/podman/5.3.2 (201 files, 80MB) *
  Poured from bottle using the formulae.brew.sh API on 2025-01-23 at 11:28:05
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/p/podman.rb
License: Apache-2.0 AND GPL-3.0-or-later
==> Dependencies
Build: go ✘, go-md2man ✘, make ✘
==> Requirements
Required: macOS >= 13 (or Linux) ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
In order to run containers locally, podman depends on a Linux kernel.
One can be started manually using `podman machine` from this package.
To start a podman VM automatically at login, also install the cask
"podman-desktop".

zsh completions have been installed to:
  /usr/local/share/zsh/site-functions
==> Analytics
install: 11,957 (30 days), 33,192 (90 days), 185,800 (365 days)
install-on-request: 11,013 (30 days), 31,176 (90 days), 165,940 (365 days)
build-error: 2 (30 days)

I also tried to create an issue regarding this bug, but it looks like I need to get rid of some unrelated warnings before being allowed to...

[michtesar]

I can confirm this, a workaround was to remove podman with brew and install it manually from the official website and follow the onboarding process that also install podman CLI. I have tried to provide a correct version of gvproxy, chmod the gvproxy folder, restart podman machine, nothing worked.

[daeho-ro]

Maybe it was fixed?

• podman: revert gvproxy bump homebrew-core#205303