Skip to content

Conversation

@rajasec
Copy link
Contributor

@rajasec rajasec commented Sep 23, 2015

Removing pausing state from error conditions, as container pause(freeze) state of the container

Signed-off-by: Rajasekaran [email protected]

@crosbymichael
Copy link
Member

why? this is a valid error, i don't see why to remove this because you cannot start another process in a container that is paused.

@rajasec
Copy link
Contributor Author

rajasec commented Sep 24, 2015

@crosbymichael
While I was doing checkpoint for paused container, it use to freeze for sometime. Once the container is resumed, it will start dumping( not an better analogy).
I thought it will applicable to start of another process too
Also I have seen this error variable is not consumed in the code. Moreover if #218 is part of runc, do we need this error condition. we can give the status to the user saying "Container in paused state"
even when we are killing cgroup processes, we are moving to frozen state ( as per the current impl).So I had an impression that pausing can not be an error condition ( rather it is the state of the container).
May be I'm missing some big picture ?

@crosbymichael
Copy link
Member

@rajasec it is an error condition if you are trying to exec another process in a paused container.

i.e.

  1. Start container
  2. Pause it
    3 . Start another process in container
    4 . Should get the error.

@crosbymichael
Copy link
Member

@rajasec in #311 we are actually using the paused error code correctly now so I don't think we need to remove it. Its was just a bug that it was not being consumed.

stefanberger pushed a commit to stefanberger/runc that referenced this pull request Sep 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants