opencontainers / opencontainers/runc
Exec cli execSetns func receive pid but findProcess failed
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
When I execute the runc exec command, I receive the pid information, but it finally fails to find the corresponding process by pid. because if it fails somewhere else inside the execSetns function there will be an error log, but it doesn't.it can only error in os.FindProcess.The error log is as follows：
so, what is mistake about exit status 15？why it happens
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
The report points to runc's exec command, the execSetns function, and the os.FindProcess call. Start by tracing that path and reproducing the reported PID failure and exit status 15; done means the failure cause is identified and an appropriate diagnostic or fix is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100