opencontainers / opencontainers/runc
Drop in-container /proc requirement?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Description
Spun off from #1726, it would be nice to not require /proc inside containers. Current blockers:
- capabilities loading, but with syndtr/gocapability#14 landed I'll be able to fix that (filed as #1735).
- closing extra file descriptors, but we can handle that before leaving the host mount namespace.
- opening the
start-signal FIFO, but we can inherit a socket through from outside withough reopening.
Do we need /proc for anything else? @cyphar seems to imply we do (or I'm reading him wrong). This is definitely an edge case, but I'd like to get it working.
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 with the blockers listed in the issue, especially libcontainer/utils/utils_unix.go and libcontainer/standard_init_linux.go, then read the discussion in #1726 and the capabilities follow-up in #1735. Confirm every remaining /proc dependency and define done as starting a container successfully without /proc mounted inside it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100