Is it possible to create netns for a container before starting it?
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 875
- PR merge metrics
- No merged PRs in 30d
Description
I've tried to create a netns and mount it in the sandboxkey path received in the Join() request but after return to request Docker doesn't use my netns but it unmount my netns, creates another one and remount it in sandoboxkey.
So, is it possible to create netns for a container before starting it?
Contributor guide
No contributing guide indexed for this repository
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 tracing the Join() request and the sandboxkey network-namespace lifecycle described in the issue. Determine whether a namespace can be created before the container starts and whether Docker replaces it; done should be a documented, reproducible answer or a clearly scoped implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100