-
Notifications
You must be signed in to change notification settings - Fork 3.3k
libpod: add next-exit/not-running/removed wait conditions (fixes #27423) #28976
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
Open
dcermak
wants to merge
1
commit into
podman-container-tools:main
Choose a base branch
from
dcermak:container-wait
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -36,6 +36,24 @@ const ( | |
| ContainerStateStopping ContainerStatus = iota | ||
| ) | ||
|
|
||
| // Wait condition strings that do not map 1:1 to a ContainerStatus. | ||
| // These mirror Docker's wait condition names so users have a way to | ||
| // express "block until the container next dies" or "block until the | ||
| // container is removed", regardless of the container's current state. | ||
| const ( | ||
| // ContainerWaitConditionNextExit waits for the next exit event, | ||
| // regardless of the container's current state. This differs from | ||
| // "exited"/"stopped", which return immediately for a container that | ||
| // has never been started. | ||
| ContainerWaitConditionNextExit = "next-exit" | ||
|
Contributor
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. Why not use |
||
| // ContainerWaitConditionNotRunning matches any state that is not | ||
| // "running" (configured, created, stopped, exited, removing). | ||
| ContainerWaitConditionNotRunning = "not-running" | ||
| // ContainerWaitConditionRemoved waits until the container has been | ||
| // removed. | ||
| ContainerWaitConditionRemoved = "removed" | ||
| ) | ||
|
|
||
| // ContainerStatus returns a string representation for users of a container | ||
| // state. All results should match Docker's versions (from `docker ps`) as | ||
| // closely as possible, given the different set of states we support. | ||
|
|
||
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
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 think these wait logics are implemented in compat API
pkg/api/handlers/utils/containers.go(waitNextExit,waitNotRunning,waitRemoved). I would reuse them.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.
agreed this should be deduplicated with the API code
if the libpod code can no handl ethese states they could be dropped out of the compat API to avoid differtent special handling.