mirror of
https://github.com/containers/podman.git
synced 2025-08-06 19:44:14 +08:00
Fix documentation of --network-cmd-path
CLI option
The `--network-cmd-path` CLI option only affects rootless networks using `slirp4netns(1)`, not `pasta(1)`. Following #18568 Podman should rather use the more generic `r.config.FindHelperBinary()` method (and therefore honour the `helper_binaries_dir` config) to find the path to the `slirp4netns` binary and deprecate the misleading `--network-cmd-path` CLI option. However, since this wasn't implemented yet we can't deprecate `--network-cmd-path` as of now. Adding a note anyway. Fixes #18560 Signed-off-by: Daniel Rudolf <github.com@daniel-rudolf.de>
This commit is contained in:
@ -83,7 +83,7 @@ Remote connections use local containers.conf for default.
|
||||
Log messages at and above specified level: debug, info, warn, error, fatal or panic (default: "warn")
|
||||
|
||||
#### **--network-cmd-path**=*path*
|
||||
Path to the command binary to use for setting up a network. It is currently only used for setting up a slirp4netns(1) or pasta(1) network. If "" is used then the binary is looked up using the $PATH environment variable.
|
||||
Path to the `slirp4netns(1)` command binary to use for setting up a slirp4netns network. If "" is used then the binary is looked up using the $PATH environment variable.
|
||||
|
||||
#### **--network-config-dir**=*directory*
|
||||
|
||||
|
Reference in New Issue
Block a user