Opened 3 years ago
Closed 3 years ago
#63489 closed defect (fixed)
'podman machine start' can't find /usr/libexec/podman/gvproxy
| Reported by: | breun (Nils Breunese) | Owned by: | judaew (Vadym-Valdis Yudaiev) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | judaew (Vadym-Valdis Yudaiev) | |
| Port: | podman |
Description
I found https://podman.io/blogs/2021/09/06/podman-on-macs.html, which explains how to use Podman on a Mac. The article explains how to install podman via Homebrew, but of course I wanted to use MacPorts instead.
First I ran sudo port install podman, which indeed gave me version 3.3.1, just like in the article.
Then when I ran podman machine init, I got an error message saying that a qemu binary could not be found. I am not sure if qemu should be a dependency of podman or if it makes sense to not install that by default, but I installed it by running sudo port instal qemu. Afterwards running podman machine init succeeded.
The next step is running podman machine start, but that gives me this error:
❯ podman machine start Error: unable to start host networking: "stat /usr/libexec/podman/gvproxy: no such file or directory"
The /usr/libexec prefix struck me as problematic, since all of the podman files are under my MacPorts prefix of /opt/local, but port contents podman doesn't list a binary called gvproxy at all and I wouldn't know what to install to get it, so this is where I got stuck.
Change History (7)
comment:1 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)
| Cc: | judaew added |
|---|
comment:2 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)
comment:4 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)
Next time, you can add a maintainer (GitHub handle) to the "Owned by" field. Thus, a maintainer receive a notification about a new ticket by email. In any case, I am always pleased to receive personal emails.
comment:5 follow-up: 6 Changed 3 years ago by breun (Nils Breunese)
Thanks. I thought I remembered a Trac ticket would automatically be assigned to the maintainer of the port, but that didn't happen.
comment:6 Changed 3 years ago by mf2k (Frank Schima)
Replying to breun:
Thanks. I thought I remembered a Trac ticket would automatically be assigned to the maintainer of the port, but that didn't happen.
That has never been the case.
comment:7 Changed 3 years ago by judaew (Vadym-Valdis Yudaiev)
| Owner: | set to judaew |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Hello, Nils
Thanks for reporting the issue. I created PR to fix this issue https://github.com/macports/macports-ports/pull/12229. It will take some time for the PR to be accepted.