Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI:DOCS] docs/build_osx.md: Describe external gvproxy #21110

Merged
merged 1 commit into from
Jan 3, 2024
+14 −0
Merged

[CI:DOCS] docs/build_osx.md: Describe external gvproxy #21110

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions build_osx.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,20 @@ The binary will be located in bin/
$ ls -l bin/
```

### Using gvproxy from homebrew, with podman from git

Recent podman builds depend on a `gvproxy` binary which comes from [containers/gvisor-tap-vsock](https://github.com/containers/gvisor-tap-vsock). A common development scenario may be using the podman desktop app as a baseline, with a development
binary of `podman` you build from git. To ensure that the podman you build here can find the gvproxy installed from podman desktop, use:

`make podman-remote HELPER_BINARIES_DIR=/opt/podman/bin`

(Also note that because the `Makefile` rules do not correctly invalidate the binary when this variable changes,
so if you already have a build you'll need to `rm bin/darwin/podman` first if you have an existing build).

Alternatively, you can set `helper_binaries_dir=` in `~/.config/containers/containers.conf`.

### Building docs

If you would like to build the docs associated with Podman on macOS:
```
$ make podman-remote-darwin-docs
Expand Down