-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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.
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
podman: Added find slirp4netns binary file from helper_binaries_dir #18620
podman: Added find slirp4netns binary file from helper_binaries_dir #18620
Conversation
You must sign your commits. Also does this require any man page changes? @Luap99 PTAL |
Thanks @HirazawaUi 👍 Can you please also add deprecation notices to uses of Line 441 in a58ea23
Yes, that would be appreciated as per discussion in #18560. To be more precise: The docs should explain the fallback to podman/docs/source/markdown/podman.1.md Lines 85 to 86 in a58ea23
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
code change LGTM but I would like to see the documentation change as mentioned by @PhrozenByte
Changes LGTM |
b7fb86e
to
258e87c
Compare
Thanks for the reminder, I have finished the signature and modified the docs |
There are so many places to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @HirazawaUi
Just some docs stuff. LGTM besides those small things 👍
Note: I can't say anything about the actual code changes 😉
docs/source/markdown/podman.1.md
Outdated
@@ -83,7 +83,8 @@ 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 `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. | |||
Path to the `slirp4netns(1)` command binary to use for setting up a slirp4netns network. If "" is used, then the binary will be searched for from the helper_binaries_dir. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Path to the `slirp4netns(1)` command binary to use for setting up a slirp4netns network. If "" is used, then the binary will be searched for from the helper_binaries_dir. | |
Path to the `slirp4netns(1)` command binary to use for setting up a slirp4netns network. If "" is used, then the binary will first be searched using the `helper_binaries_dir` option in `containers.conf`, and second using the `$PATH` environment variable. |
Explain what helper_binaries_dir
is and still mention $PATH
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good suggestion
docs/source/markdown/podman.1.md
Outdated
@@ -83,7 +83,8 @@ 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 `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. | |||
Path to the `slirp4netns(1)` command binary to use for setting up a slirp4netns network. If "" is used, then the binary will be searched for from the helper_binaries_dir. | |||
It will be deprecated in Podman 5.0. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will be deprecated in Podman 5.0. | |
**Note:** This option is deprecated and will be removed with Podman 5.0. Use the `helper_binaries_dir` option in `containers.conf` instead. |
The option is deprecated as of now (resp. the next version this happens to get merged into); it might be removed with Podman 5.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just thinking about it: Doesn't this imply a user facing change?
Cc: @Luap99
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good suggestion, this is supposed to be a user facing change, I will add it later
cmd/podman/root.go
Outdated
@@ -439,6 +439,7 @@ func rootFlags(cmd *cobra.Command, podmanConfig *entities.PodmanConfig) { | |||
_ = cmd.RegisterFlagCompletionFunc(conmonFlagName, completion.AutocompleteDefault) | |||
|
|||
// TODO (5.0): remove this option with the next major release after https://github.com/containers/podman/issues/18560 was implemented |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// TODO (5.0): remove this option with the next major release after https://github.com/containers/podman/issues/18560 was implemented | |
// TODO (5.0): --network-cmd-path is deprecated, consider removing it |
There's no need to still reference the issue. You can also merge this with the next line if you want to.
I agree that adding notices to every use is a bit tedious...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree not to reference this issue, but I think --network-cmd-path is deprecated, remove this option with the next major release
would be better.
[NO NEW TESTS NEEDED] Fixes: containers#18568 Signed-off-by: binghongtao <[email protected]>
258e87c
to
2974936
Compare
LGTM, thanks @HirazawaUi for your work and considering the suggestions! 👍 |
/aprove |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: HirazawaUi, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[NO NEW TESTS NEEDED]
Fixes: #18568
Does this PR introduce a user-facing change?