opencontainers / opencontainers/runc
runc can not wait process in the container exits when share pid namespace
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
Description
1.docker run with --pid=host
2.other processes in the container except the init process D live
3.docker rm -f $containerdID
Steps to reproduce the issue
Describe the results you received and expected
i received:
1.containerd-shim and init process reaped
2.container cgroup residue
What version of runc are you using?
[root@localhost ~]# runc --version
runc version 1.1.3
commit: 02a436f4f2efd8c5a2ec5c4ed3d196242d4edb77
spec: 1.0.2-dev
go: go1.17.3
libseccomp: 2.5.3
Host OS information
No response
Host kernel information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported docker run --pid=host and docker rm -f sequence with runc 1.1.3, then inspect how runc waits for and reaps processes when the container shares the host PID namespace. Done means the container exits cleanly without a reaped init or shim and without leftover cgroup state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100