Skip to content
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.

Sign up for GitHub

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

Fix a regression when killing and deleting a container with shared(host) pid namespace #4048

Closed
wants to merge 5 commits into from
+71 −18
Closed

Fix a regression when killing and deleting a container with shared(host) pid namespace #4048

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
810c5f0
kill all processes in container without private pid ns
lifubang Oct 2, 2023
120dad4
kill all processes in container without private pid ns before destory
lifubang Oct 2, 2023
04fc3fe
increase the retry times from 5 to 10 when removing cgroup paths
lifubang Oct 10, 2023
48ff07c
never ignore cgroup destroy error for runc-delete
lifubang Oct 10, 2023
9225eaa
add a testcase for runc delete the container with host pid ns
lifubang Nov 6, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions libcontainer/container_linux.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -873,6 +873,26 @@ func (c *Container) newInitConfig(process *Process) *initConfig {
func (c *Container) Destroy() error {
c.m.Lock()
defer c.m.Unlock()
if !c.config.Namespaces.IsPrivate(configs.NEWPID) {
Copy link
Contributor

Choose a reason for hiding this comment

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

I am very much against doing this. Kill should do all the killing, and Destroy should remove the files. This was all mixed up before, but I got it untangled in #3825 (alas, with a couple of regressions which you have reported in #4047).

The alternative to doing this, without mixing the kill and destroy again, is this: 7de61c4 (PTAL 🙏🏻)

Copy link
Member Author

Choose a reason for hiding this comment

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

But I think we can't force users to use runc kill before runc delete if the container is in stopped state.

const retries = 10
for i := 0; i < retries; i++ {
pids, err := c.cgroupManager.GetAllPids()
if c.ignoreCgroupError(err) != nil {
return err
}
if len(pids) > 0 {
if err := signalAllProcesses(c.cgroupManager, unix.SIGKILL); c.ignoreCgroupError(err) != nil {
return err
}
if i == retries-1 {
return errors.New("some processes are still running in the container")
}
time.Sleep(100 * time.Millisecond)
} else {
break
}
}
}
return c.state.destroy()
}

Expand Down