This repository has been archived by the owner on May 6, 2020. It is now read-only.
kill: Deadlock waiting for a kill to be completed #130
Comments
sboeuf
pushed a commit
that referenced
this issue
Oct 12, 2017
This commit updates runc vendoring, the most important reason is that we want the fix of opencontainers/runc#1609 to be included into our agent. Fixes #130 Signed-off-by: Sebastien Boeuf <[email protected]>
sboeuf
pushed a commit
that referenced
this issue
Oct 12, 2017
Even if the source of our kill deadlock bug has been solved through libcontainer directly, we might want to avoid any potential lock when issuing a signal to a container. That's why this patch introduces a timeout after which we consider the kill command as failing. Moreover, it will show us easily if we're getting caught in such a case in the future, by printing important logs. Fixes #130 Signed-off-by: Sebastien Boeuf <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In few cases, we end up waiting forever for our container to be signalled. This issue comes from a libcontainer issue here: opencontainers/runc#1609 that has been solved with opencontainers/runc#1610
We need to re-vendor our agent in order to get the fix.
The text was updated successfully, but these errors were encountered: