opencontainers / opencontainers/runc
runc init can't communicate with runc start
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
Description
runc init can't send message to runc start if use exec.fifo.
Steps to reproduce the issue
runc init can't send message to runc start if use exec.fifo.
Describe the results you received and expected
runc init can send message to runc start by using exec.sock
What version of runc are you using?
1.12
Host OS information
any kernel
Host kernel information
any
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 communication failure in runc 1.12 with exec.fifo, then compare it with the expected exec.sock behavior. Trace the init/start communication path to identify where the message is lost; done means runc init can communicate with runc start through exec.fifo on the stated environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100