Sysbox Nesting (future support?)
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.9k
- Forks
- 230
- Avg merge
- 7h 48m
- Merged PRs (30d)
- 3
Description
I understand that sysbox nesting is currently a limitation.
Is this a feature that is ever planned on being supported in the future?
I'm aware of some solutions like this Y Combinator comment. However, this comes with it's drawbacks as mentioned in the well known "Using Docker-in-Docker for your CI or testing environment? Think twice." blog post.
I can see this being a common use case such as for a CI server:
- You run your CI server in a docker container.
- Each build job runs inside a container
- The build jobs would like to do things like build, publish, etc.
For this case, 3 levels deep may be adequate, but I'm sure there are less common but valid use cases which would involve many more levels of nesting.
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 docs/user-guide/limitations.md and its Sysbox nesting section to understand the stated limitation and the linked context. The issue does not name implementation files or tests; progress would require defining the supported nesting behavior and confirming whether the project has a current plan for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100