Contributing AIO Sandbox Image
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- dockerfile
- Domain
- infrastructure
Research direction
Start by reviewing the repository's Dockerfile expectations and the proposed image, ghcr.io/agent-infra/sandbox:latest. Done means the contribution approach is decided and the required repository changes, if any, are identified.
Written by the indexing model from the issue text.
Description
Hi, we would like to contribute our AIO Sandbox project image to OpenShell community.
AIO Sandbox & NVIDIA OpenShell seem to complement each other quite well. AIO Sandbox provides rich built-in agent capabilities such as browser automation, shell access, file operations, VS Code Server, and MCP integration. It provides inner execution environment where the agent actually performs work.
OpenShell, on the other hand, provides the secure outer runtime boundary: sandbox lifecycle management, policy enforcement, controlled networking, and operational governance.
Please see the detail blog we recently published to this regards.
One question I have regarding the contribution process. Instead of including the detail execution steps in the DOCKERFILE, could we just specify the original image instead (ghcr.io/agent-infra/sandbox:latest).
Look forward to hearing from you. Thanks.
- Dominant language
- Dockerfile
- Stars
- 191
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
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.
More from NVIDIA/OpenShell-Community
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
opencode sandbox policy: npm child-process CONNECT denied (ECONNRESET) and no Vertex AI / WIF egress Open
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in NVIDIA/OpenShell-Community
Similar issues
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/prow#953 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
conceptadev/noir#95 ·
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100