-
Notifications
You must be signed in to change notification settings - Fork 2.2k
libcontainer: remove "pausing" state #3360
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
Conversation
| Restore(process *Process, criuOpts *CriuOpts) error | ||
|
|
||
| // If the Container state is RUNNING or CREATED, sets the Container state to PAUSING and pauses | ||
| // If the Container state is RUNNING or CREATED, sets the Container state to PAUSED and pauses |
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.
Although the actual state that Pause internally sets is FROZEN, I hope this should be okay as an externally exposed func doc? cc/ @kolyshkin
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.
Yes, it's "frozen" in cgroup lingo, and "paused" in libcontainer lingo.
Signed-off-by: danishprakash <[email protected]>
055d2fd to
7346dda
Compare
kolyshkin
left a comment
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.
LGTM
That issue also says to convert docs to golang style, so we can't close it just yet. Surely this needs to be a separate PR. So, replace |
|
Yes, that can be a separate PR of its own. Updated. |
|
@thaJeztah PTAL |
thaJeztah
left a comment
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.
LGTM, thanks for contributing!
Upon running tests via
make test, I encountered flaky failures, I'll look into those and see if they have something to do with my host because I noticed the same behavior onmaintoo.Addresses #3343