opencontainers / opencontainers/runc
Reasons that can't use runc-dmz
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
When we were introducing dmz to runc, we have realized that there were 3 reasons we should disable runc-dmz:
- runc-dmz does not play well with selinux #4057, fixed by #4053.
- The container process has a
CAP_SYS_PTRACEability, fixed by #3987. - If the container process is not root and the capabilities are not in the ambient set #4125, will be fixed by #4137.
Maybe there are some more scenarios that can't use runc-dmz, please provide to help us improve or deprecate it. Thanks.
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 reviewing the linked issues #4057 and #4125 and their fixes (#4053, #3987, and #4137), then inspect the runc-dmz behavior involved in SELinux, CAP_SYS_PTRACE, and ambient capabilities. Done means documenting any additional scenarios that fail, or producing a clear proposal to improve or deprecate runc-dmz.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100