[macOS] Cannot start VM with podman machine start because it tries to start gvproxy from /usr/libexec/podman/gvproxy

[tnk4on]

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

When I run podman machine start even though I have placed gvproxy in a valid execution path, I get an error that gvproxy is not found in the path and cannot start the VM.

Steps to reproduce the issue:

On the Mac client:

1. Get the Podman 3.3.0-rc2 source code and build it

2. Get the gvproxy binary and place it in execution path

$ wget https://github.com/containers/gvisor-tap-vsock/releases/download/v0.1.0/gvproxy-darwin
$ chmod 755 gvproxy-darwin
$ mv gvproxy-darwin /usr/local/bin/gvproxy

3. Run "podman machine start", it will stop with an error.

$ podman machine start
Error: unable to start host networking: "stat /usr/libexec/podman/gvproxy: no such file or directory"

Describe the results you received:

I can't create directories under /usr/libexec/ even if I have root privileges.

$ sudo mkdir /usr/libexec/podman
Password:
mkdir: /usr/libexec/podman: Operation not permitted

The reason is that System Integrity Protection is currently enabled in macOS.
https://support.apple.com/en-us/HT204899

Describe the results you expected:

The VM will be successfully started.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

$ podman version
Client:
Version:      3.3.0-dev
API Version:  3.3.0-dev
Go Version:   go1.16.6
Git Commit:   a5adadf83b0f11c168563d1f26ebb7535cab4b9c-dirty
Built:        Sat Aug 14 04:00:57 2021
OS/Arch:      darwin/amd64

Package info (e.g. output of rpm -q podman or apt list podman):

v3.3.0-rc2
https://github.com/containers/podman/archive/refs/tags/v3.3.0-rc2.tar.gz

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)

Yes

Additional environment details (AWS, VirtualBox, physical, etc.):

• MacBook Pro (13-inch, 2017, Two Thunderbolt 3 ports)
• macOS Big Sur Version 11.4

[rhatdan]

@ashley-cui Are we not shipping gvproxy?

[ashley-cui]

@rhatdan I'm currently working on shipping it via homebrew. Though the gvproxy is not shipped in our tarball that's downloaded from github artifacts.

[baude]

ill take this one ...

[ashley-cui]

@baude just FYI, homebrew doesn't automatically symlink libexec.install (it does for every other location but not libexec) got me tripped up on Thursday..

[tnk4on]

I was able to podman machine start using the updated v3.3 branch.
Thanks!

$ which gvproxy
/usr/local/bin/gvproxy
$ rm -rf /var/folders/df/vy1htn753fd_w4420rltfg0w0000gn/T/podman/qemu_podman-machine-default.sock
$ podman machine start
INFO[0000] waiting for clients...
INFO[0000] listening tcp://0.0.0.0:7777
INFO[0000] new connection from  to /var/folders/df/vy1htn753fd_w4420rltfg0w0000gn/T/podman/qemu_podman-machine-default.sock
Waiting for VM ...
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.svm [bit 2]
$ podman version
Client:
Version:      3.3.0-dev
API Version:  3.3.0-dev
Go Version:   go1.16.6
Git Commit:   39cab790cc90c77d4b4a156f5f885077b267cbd9
Built:        Tue Aug 17 10:21:08 2021
OS/Arch:      darwin/amd64

Server:
Version:      3.2.3
API Version:  3.2.3
Go Version:   go1.16.6
Built:        Tue Aug  3 04:39:21 2021
OS/Arch:      linux/amd64