Skip to content

Handle instances where runc cannot be killed because it is not running [3/3]#6632

Open
glightfoot wants to merge 2 commits intomoby:masterfrom
glightfoot:handle-runc-not-running
Open

Handle instances where runc cannot be killed because it is not running [3/3]#6632
glightfoot wants to merge 2 commits intomoby:masterfrom
glightfoot:handle-runc-not-running

Conversation

@glightfoot
Copy link
Copy Markdown

This final PR handles instances where runc has died and cannot be killed. Unfortunately, this is just string matching, but I couldn't find a better way to do it since we're dealing with shell ooutput.

Related PR's:
#6630
#6631

Fixes: #4483

Signed-off-by: Greg Lightfoot <greg.lightfoot@reddit.com>
Signed-off-by: Greg Lightfoot <greg.lightfoot@reddit.com>
@crazy-max crazy-max mentioned this pull request Apr 1, 2026
4 tasks
Copy link
Copy Markdown
Member

@tonistiigi tonistiigi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you put together a reproduction case of integration test instead. The fix does n't look correct as you shouldn't return out from a failure to send a signal. The question would be why doesn't any current end mechanisms like context ending or p.ended trigger if container is dead.

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.

Buildkitd logs "failed to kill process in container id <cid>: buildkit-runc did not terminate successfully: container not running" for hours

2 participants