-
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
Add podman run --timeout option #10119
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -83,6 +83,11 @@ type ContainerBasicConfig struct { | |
// instead. | ||
// Optional. | ||
StopTimeout *uint `json:"stop_timeout,omitempty"` | ||
// Timeout is a maximum time in seconds the container will run before | ||
// main process is sent SIGKILL. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So is this immediate SIGKILL, or does it use the normal stop logic (SIGTERM -> timeout -> SIGKILL)? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We are using the conmon --timeout flag, which is defined as
Which to me means the KILL signal gets sent. I don't think we should make it more complicated then this. If users want more complicated they should do it via bash. |
||
// If 0 is used, signal will not be sent. Container can run indefinitely | ||
// Optional. | ||
Timeout uint `json:"timeout,omitempty"` | ||
// LogConfiguration describes the logging for a container including | ||
// driver, path, and options. | ||
// Optional | ||
|
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.
We point at conmon here and a few other places in this and the other man pages, but we don't explain it's relationship with Podman anywhere. Not for this PR, but we should probably do so.
In the shorter term, the common(8) man page now exists. Can you add a a ptr to that and to the other manpages in here please?
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.
#10134