opencontainers / opencontainers/runc
signaling init process caused "permission denied" -> which signal?
Open
Nobody has claimed this yet.
kind/question
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
I'm getting:
Feb 24 16:00:16 admin podman[20703]: time="2020-02-24T16:00:16+01:00" level=error msg="container_linux.go:389: signaling init process caused \"permission denied\""
Feb 24 16:00:16 admin podman[20703]: container_linux.go:389: signaling init process caused "permission denied"
Feb 24 16:00:16 admin podman[20703]: Error: permission denied
But which signal caused this? Unfortunately the error message doesn't contain the actual signal.
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 at container_linux.go:389, where the reported "signaling init process" error is emitted, and trace how the signal failure is returned. Determine which signal information is available at that point and make the error identify it. Verify the resulting error output with the relevant runc process-signaling tests, if present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100