osep: add OSEP-0004 secure container runtime support#177
Merged
jwx0925 merged 5 commits intoalibaba:mainfrom Feb 11, 2026
Merged
osep: add OSEP-0004 secure container runtime support#177jwx0925 merged 5 commits intoalibaba:mainfrom
jwx0925 merged 5 commits intoalibaba:mainfrom
Conversation
hittyt
requested review from
Generalwin,
Pangjiping,
Spground,
fengcone,
jwx0925,
kevinlynx and
ninan-nn
as code owners
fengcone
reviewed
Feb 5, 2026
fengcone
reviewed
Feb 5, 2026
jwx0925
reviewed
Feb 5, 2026
Collaborator
|
@codex review |
|
Codex Review: Didn't find any major issues. Nice work! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
- Fix Firecracker positioning: not a standalone OCI runtime, only available via Kata Containers (kata-fc) in Kubernetes mode - Add pooled sandbox runtime consistency validation (409 Conflict) - Cover both K8s providers (BatchSandbox + AgentSandbox) - Add kata-fc RuntimeClass and containerd config examples - Refine compatibility matrix, performance data, and test plan Co-authored-by: Cursor <cursoragent@cursor.com>
Collaborator
|
LGTM |
Pangjiping
requested changes
Feb 8, 2026
Pangjiping
requested changes
Feb 8, 2026
Pangjiping
requested changes
Feb 8, 2026
Replace per-request runtime selection with server-level configuration. The secure runtime is now an infrastructure decision managed by administrators, requiring no API or SDK changes. Co-authored-by: Cursor <cursoragent@cursor.com>
Pangjiping
previously approved these changes
Feb 9, 2026
jwx0925
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OpenSandbox executes untrusted AI-generated code. Standard container isolation (runc) may not provide sufficient protection against container escape attempts. Secure container runtimes provide hardware-level isolation to protect the host system.
This PR add OSEP-0004: Pluggable Secure Container Runtime Support - a design proposal for integrating secure container runtimes (gVisor, Firecracker, Kata Containers) into OpenSandbox.
Testing
Breaking Changes
Checklist