Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

sharePidns would cause zombie process leak in the container #803

Closed
lifupan opened this issue Jul 7, 2020 · 3 comments
Closed

sharePidns would cause zombie process leak in the container #803

lifupan opened this issue Jul 7, 2020 · 3 comments
Assignees
Labels
bug Incorrect behaviour

Comments

@lifupan
Copy link
Member

lifupan commented Jul 7, 2020

Description of problem

Since the sharedpidns init process hasn't the child reap function, thus there is no init process would reap
the zombie process in the container. for much info please see kata-containers/runtime#2794 (comment).

Expected result

(replace this text with an explanation of what you thought would happen)

Actual result

(replace this text with the output of the kata-collect-data.sh script, after
you have reviewed its content to ensure it does not contain any private
information).

@lifupan lifupan added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Jul 7, 2020
@lifupan lifupan self-assigned this Jul 7, 2020
@ariel-adam
Copy link

@lifupan Could clarify this bug?
What exactly is the problem including the expected result and actual result

@jodh-intel
Copy link
Contributor

Hi @lifupan - please could you clarify - is this still an issue? If not, please could you provide the issue/PR number?

@jodh-intel jodh-intel removed the needs-review Needs to be assessed by the team. label Sep 8, 2020
@lifupan
Copy link
Member Author

lifupan commented Sep 9, 2020

Hi @lifupan - please could you clarify - is this still an issue? If not, please could you provide the issue/PR number?

Hi @jodh-intel

Actually this issue is specific to share sandboxpidns when createsandbox requested as https://github.com/kata-containers/agent/blob/master/grpc.go#L1490. But by now it seemed we hadn't used this feature, and we only do share the sandbox pid ns with the pause container's init process instead of create an separated pause process, thus I think I can close this issue temporarily.

@lifupan lifupan closed this as completed Sep 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Incorrect behaviour
Projects
None yet
Development

No branches or pull requests

3 participants