docs: refactored _Troubleshooting Podman on macOS_ #3207
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Fabrice Flore-Thébault <[email protected]>
themr0c
requested review from
jeffmaury and
lstocchi
and removed request for
a team
benoitf
requested changes
Jul 18, 2023
Comment on lines
-9
to
-29
| #### Issue | ||
|
|
||
| When setting a custom binary path (under Preferences -> Custom binary path), Podman is unable to find `gvproxy` and `podman-mac-helper`: | ||
|
|
||
| ```sh | ||
| 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 $BINDIR/../libexec/podman]. To resolve this error, set the helper_binaries_dir key in the `[engine]` section of containers.conf to the directory containing your helper binaries." | ||
| ``` | ||
|
|
||
| #### Solution | ||
|
|
||
| 1. Download `gvproxy` from the [gvisor-tap-vsock release page](https://github.com/containers/gvisor-tap-vsock/releases). | ||
| 2. Build the `podman-mac-helper` from the source code on the [Podman GitHub page](https://github.com/containers/podman/tree/main/cmd/podman-mac-helper). | ||
| 3. Add the `helpers_binaries_dir` entry to `~/.config/containers/conf`: | ||
|
|
||
| ```sh | ||
| [containers] | ||
|
|
||
| helper_binaries_dir=["/Users/user/example_directory"] | ||
| ``` | ||
|
|
||
| **NOTE**: A pre-built binary will be added to the Podman release page so you do not have to build `podman-mac-helper`. An [issue is open for this](https://github.com/containers/podman/issues/16746). |
There was a problem hiding this comment.
This can be still an issue if you select a custom binary path for Podman (not the main use case but it can happen)
so probably keep it
Comment on lines
-35
to
-37
| Despite having Podman Engine installed, you might receive an error as follows - | ||
| `Error: No such keg: /usr/local/Cellar/podman` | ||
| or any similar error denoting that Podman Engine does not exist. |
There was a problem hiding this comment.
where did it go ?
it's the error message that people could see (and browser engine can parse) to come to this page
|
Too complex to modify using the Android app. It will have to wait. For clarity you could convert to draft. |
|
@themr0c ok, switched to draft as you requested |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Refactored Troubleshooting Podman on macOS.
Screenshot/screencast of this PR
What issues does this PR fix or reference?
refs #3045
How to test this PR?