opencontainers / opencontainers/runc
seccomp: officially define the list of syscalls required by runc itself
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
There are some syscalls that needs to be enabled to use seccomp mode, but currently these syscalls are not documented.
Also wondering OCI Runtime Spec needs to be revised https://github.com/opencontainers/runtime-spec/blob/a950415649c735f9fd9ec3b8869efef24b67cef4/config-linux.md#seccomp
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 how runc uses seccomp and identify the syscalls required by runc itself. Then compare the findings with the linked OCI Runtime Spec config-linux.md seccomp section. Done means the required syscall list is documented and any needed OCI Runtime Spec revision is clearly identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100