-
Notifications
You must be signed in to change notification settings - Fork 2.6k
document --service-container
on podman-kube-play
#25708
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
base: main
Are you sure you want to change the base?
Conversation
This flag was added on Podman v4.4.0 but was not documented. Signed-off-by: Alexandre Morignot <erdnaxeli@cervoi.se>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: erdnaxeli The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I just read this:
As this flag can be seen with
|
The reason we hide because we only use it for the systemd integration and don't expect users to use that directly as such it is hidden. It is not stable as we can change it anytime what it does internally. As such I don't think it should be documented. If it would be it would have to sat it is not stable and not supposed to be used outside of systemd. |
I understand why it is hidden, but I saw it in the output of |
A friendly reminder that this PR had no activity for 30 days. |
It'd be a good idea to document it, even if it's a flag not intended for end users. But as @Luap99 suggested, if we choose to document this, we should mention the fact that it's meant for systemd integration and perhaps that it's subject to changes as well. |
This flag was added on Podman v4.4.0 but was not documented.
Does this PR introduce a user-facing change?