First release candidate on the 1.3.0 feature line, cut from release-1.2.1 (2026-11-13). Headline: fast-sandbox rootfs-only snapshots reach the public lifecycle API across all five SDKs, and the OSEP-0018 execd-as-init topology becomes the server default. Also notable: request admission and fenced teardown for credential-bound egress subjects, configurable Fastlet Proxy resources, and the removal of the deprecated DevOps plain-text diagnostics surface. Baseline for every section is release-1.2.1. rc releases publish images but hold packages — SDK/CLI artifacts ship at the 1.3.0 stable bump.
Highlights
- Rootfs-only snapshots on the public API:
create_snapshot(mode="rootfsOnly")in all five SDKs — kilobyte-scale, CPU-portable artifacts that restore by cold boot;fullremains the default and pause/resume checkpoints stay full-only (#2709 #2835) - execd-as-init becomes the default: the server injects
EXECD_INIT=1so execd owns the sandbox process tree (child reaping, signal forwarding, container lifecycle), and a new privilege-reduction guide documents pairing it with the hardening floor (#2825 #2830) - Fast Sandbox hardening: Fastlet Proxy CPU/memory resources become configurable through the chart, RootfsOnly snapshot qualification self-derives from the deployed Firecracker bundle, and experimental credential-bound egress advances with request admission, drain fencing, transport teardown, and transition metrics (#2870 #2709 #2794 #2836 #2841 #2838)
Server
- Fast-sandbox rootfs-only snapshot mode is wired through the public lifecycle API:
CreateSnapshotRequest.mode: full | rootfsOnly(defaultfull) with a read-only top-levelSnapshot.mode, persisted across SQLite, PostgreSQL, and the one-shot migration; Docker and Kubernetes runtimes rejectrootfsOnlyin preflight with 409, and the fsb runtime mirrors the FastPath OCI gate before any intent is persisted (#2709) runtime.execd_run_as_initnow defaults to true: the server injectsEXECD_INIT=1so bootstrap execs intoexecd --init; set it tofalseto keep the classic background-and-wait topology (#2825)- The deprecated DevOps plain-text diagnostics surface is removed; the stable Diagnostics API (context, scoped logs/events) is unchanged, and
diagnostics/logs/eventsnow requirescope(#2826) - Security fixes:
volumeMounts.subPathvalues carrying Windows-separator traversal (foo\..\secret) or a leading backslash are rejected, closing a volume-root escape on Windows nodes (#2749); secure-access signing keys are no longer echoed in config-validation errors, including theOPENSANDBOX_SECURE_ACCESS_KEYSenv path (#2778) - Pool capacity specs where
bufferMinexceedsbufferMaxare rejected with 422, preventing the controller's create/delete oscillation; pools already applied via kubectl still list (#2801) - The server dials host-mapped sandbox ports at
docker.publish_host, so the server-side proxy and the egress sidecar readiness probe work when ports are published on a specific address (#2846) - Smaller fixes:
docker.pids_limit = 0disables the PID limit as documented (#2786); a malformed template-listmetadatafilter returns 400INVALID_METADATA_FORMATinstead of a silently empty page (#2790); renew-intent queue payloads that are valid JSON but not objects are skipped like any other malformed intent instead of logging a full worker-error traceback for each (#2791); reserved-metadata PATCH rejections return the canonicalSANDBOX::INVALID_METADATA_LABELcode on the shared Kubernetes/fsb helper and the Docker service (#2793 #2796)
SDKs
- Snapshot
mode(full|rootfsOnly) is exposed across JavaScript, Kotlin, C#, and Go, completing the Python SDK from #2709: an omitted mode stays off the wire for legacy servers, and responses without the field read back asfull(#2835) - Code-interpreter runtime probes require a confirmed zero exit in Python, JavaScript, and Kotlin, matching Go and C#:
CodeInterpreter.create()no longer resolves andisHealthy()no longer reports true when a probe stream ends without an exit code (#2807)
Python
- Caller handler exceptions in the code-interpreter SDK propagate as
SandboxExceptioninstead of being logged and swallowed mid-stream (#2697) - Legacy SSE normalization runs in linear time; large unterminated events and long leading whitespace no longer cause quadratic CPU work (#2845)
JavaScript
SandboxManager.renewSandboxreturns the renew response, so callers can see theexpiresAtthe server actually applied; source-compatible with existingawaitcall sites (#2699)
Kotlin
- The first SSE event survives a leading UTF-8 BOM, so
Execution.idis no longer null on execd streams that start with one (#2800)
C#
- Endpoint cache invalidation is scoped to the in-flight key: pausing or killing one sandbox no longer discards another sandbox's just-fetched endpoint (#2843)
Go
WatchMetricsdelivers metric snapshots as they arrive instead of buffering until the stream ends and failing to parse (#2805)
Controller
- The Helm chart's manager ClusterRole gains
pods/exec: create, fixing theRestartrecycle strategy on Helm installs — every restart exec was previously Forbidden, so pods returned to a Restart pool were never recycled; a sync test now asserts the chart never drifts from the generated role (#2780)
Execd
- The
/proxyroute reuses one shared upstream connection pool instead of dialing per request and leaking each connection for 600 seconds, so steady proxy traffic no longer accumulates sockets in execd and the sandboxed server (#2788) - Code contexts fail fast: an unusable working directory returns 400 immediately instead of retrying for five minutes and answering 500 (#2782); a context whose Jupyter session is already gone (for example after a Jupyter restart) deletes cleanly instead of failing forever and blocking language-wide deletes (#2785); listing contexts for a non-kernel language returns 400 instead of 500 (#2792)
- Path handling:
$characters that name no variable (for exampleOuter$1.class) stay literal instead of silently expanding to another path (#2779); invalid isolated-session search globs return 400 like host search (#2760); file birth time is only used when the returned inode and device match the queried entry (#2612)
Networking
egress
- [EXPERIMENTAL] The credential-bound Fast Sandbox roadmap advances on four fronts: admitted HTTP/1.1 requests are served against immutable subject dispatch snapshots with handshake-registry pinning and response-header redaction, and HTTP/2 negotiation is disabled for subject TLS (#2794); existing decrypted connections are fenced and drained on binding-removal transitions using
OPENSANDBOX_EGRESS_REVISION_DRAIN_TIMEOUT_SECONDS(#2836); subject transports are torn down on Unload, suspend, receiver failure, and shutdown, refusing source-IP reuse while old connections remain unconfirmed (#2841); and bounded transition counters and latency histograms distinguish confirmed results from pending reconciliation without leaking subject identities (#2838). The feature remains off by default;alland unset behavior is unchanged. - DNS replies to non-EDNS UDP clients are kept within 512 bytes with TC set so legacy resolvers retry over TCP, instead of receiving oversized answers with an unsolicited OPT record (#2802)
- Invalid ports in
OPENSANDBOX_EGRESS_DNS_UPSTREAMentries fail at startup like a hostname does, instead of starting normally and answering SERVFAIL for every forwarded query (#2809)
ingress
- A relayed WebSocket handshake rejection no longer truncates the backend's error body: the stale
Content-Lengthis dropped so rejections larger than 1 KiB arrive intact (#2798) - Route port segments with a leading sign (
+8080,+08080) are rejected in header and URI modes instead of silently routing to the unsigned port (#2806)
Fast Sandbox
- Fastlet Proxy CPU/memory requests and limits are configurable through
controller.fastletProxy.resources, wired to four new controller flags with quantity validation; prior fixed defaults are preserved (#2870 fast-sandbox#215) - RootfsOnly snapshot qualification now derives its digests from the deployed Firecracker bundle instead of requiring operator-provisioned profiles, with hardened qualification startup and diagnostics (#2709 fast-sandbox#185)
- FSEP-0003 proposes always-on Fastlet control-plane authentication (ServiceAccount tokens with a controller-injected allow list); the design draft lands with this pin and carries no code — no behavior changes in this release (#2870 fast-sandbox#206)
Misc
- OSEPs: OSEP-0027 drafts an optional, path-scoped E2B compatibility adapter for core agent workflows on Linux/amd64 Fast Sandbox; the proposal remains draft with unvalidated candidate versions (#2591)
- CLI:
osb config setvalidates keys and values at set time instead of failing every later command with SDK internals (#2766); a bad credential vault payload shows the parser error instead of a generic "failed to read" (#2744); the deprecatedosb devopsgroup is removed in favor ofosb diagnostics(#2823) - Console: node-agent readyz probes bracket IPv6 pod IPs so IPv6-primary clusters no longer report the DaemonSet critical (#2799);
events.k8s.ioevents show their timestamps on the K8s Events page (#2803); a tenant-filtered K8s view no longer mixes in system pods and events (#2808) - Node-agent chart: the health port is derived correctly from a
host:portserverAddr, which previously renderedcontainerPort: 0and blocked installation (#2789) - CI and tests: the execd-init container-contract tests join the gating python e2e suite instead of a non-blocking dedicated job (#2829); the fast-sandbox lane runs storage-independent scenarios once on the overlaybd lane, projected to cut the job from ~40 to ~28 minutes (#2831); the OSEP-0018 hardening floor is wired and verified on that lane, establishing that the current fsb guest kernel has no Landlock and the floor degrades per its fail-open contract (#2833); comment cleanup across cross-language e2e suites and scripts, including removal of a dead integration entry (#2821 #2822); a gin test-mode race in execd controller tests is fixed (#2842)
Upgrade & Compatibility
- execd-as-init default:
[runtime] execd_run_as_initnow defaults to true — the server injectsEXECD_INIT=1and execd owns the sandbox process tree. Deployments relying on the classic topology setexecd_run_as_init = false; fsb golden-image templates keep their baked topology until rebuilt (#2825) - DevOps routes removed:
GET /sandboxes/{id}/diagnostics/inspect,diagnostics/summary, and the scope-less plain-text fallback ondiagnostics/logs/events(including legacytail/since/container/limitparameters) are gone;scopeis required and its omission returns 422. The stable scoped Diagnostics API is unchanged, and its only known consumer was the removed CLI group (#2826 #2823) - CLI migrations:
osb devops logs|events|inspect|summaryare removed — useosb diagnostics logs <id> --scope container -o raw,osb diagnostics events <id> --scope runtime -o raw,osb sandbox get <id> -o json, andosb diagnostics context <id>(#2823);osb config setnow rejects unknown keys and invalid values at set time (#2766) - Snapshot mode: the default remains
full;rootfsOnlyrequires the fast-sandbox backend with OCI-backed sandboxes, and Docker/Kubernetes return 409UNSUPPORTED_RUNTIME. A rootfs-only restore is an explicitcreate(snapshotId=...)cold boot — processes and RAM are discarded, the entrypoint re-runs, and resume moves from milliseconds to seconds; pause/resume checkpoints stay full-only (#2709 #2835) - Fastlet Proxy resources: the new
controller.fastletProxy.resourceschart value carries CPU/memory requests and limits into the Fastlet Pod spec and the ResourceAware memory budget; defaults are unchanged, so no action is required unless you want to tune them (#2870 fast-sandbox#215) - Code-interpreter readiness: probes require a confirmed zero exit, so environments where the probe previously "passed" with an unknown exit code will now surface
SandboxReadyTimeoutException/unhealthy — investigate the runtime instead of retrying blindly (#2807) - Python handler errors: code-interpreter
ExecutionHandlersthat raise now abort the stream with aSandboxExceptioninstead of the run completing silently (#2697) - Pool validation:
capacitySpec.bufferMinabovebufferMaxreturns 422 on create and update; pools already applied with the invalid shape still list and load, but should be corrected (#2801) - Error code normalization: reserved-metadata PATCH rejections return
SANDBOX::INVALID_METADATA_LABELon all backends — clients matching the bareINVALID_METADATA_LABELliteral must update (#2793 #2796) - Docker configuration:
docker.pids_limit = 0now disables the limit (previously rejected by validation) (#2786); with[docker].publish_hostset, the server reaches published sandbox ports at that address, which changes proxy/sidecar connectivity for deployments that pinned it (#2846) - Egress DNS upstream validation:
OPENSANDBOX_EGRESS_DNS_UPSTREAMentries with an invalid port now fail sidecar startup; fix previously "accepted" values like8.8.8.8:0or8.8.8.8:70000before upgrading (#2809) - Request validation: template-list
metadatafilters with malformed segments return 400INVALID_METADATA_FORMATinstead of a silently empty page;env=still filters on the empty value (#2790);subPathvalues with Windows-separator traversal are rejected on all runtimes (#2749) - Images:
opensandbox/<component>:release-1.3.0-rc.1(all three registries; fsb images for fast-sandbox) - Packages: unchanged — SDK/CLI artifacts publish at the
1.3.0stable release - Charts: render from this tag (
helm template ./manifests/charts/opensandbox) - Kubernetes: supported range v1.21 – v1.34
- Skew: server ↔ CLI/SDK same line supported; ±1 minor warns
👥 Contributors
Thanks to these contributors ❤️
- @Aboysky
- @Jackmeson1
- @Pangjiping
- @Yeaury
- @acodercat
- @devjoinedthechat
- @fengcone
- @fxia0018
- @hpliStartAgain
- @rudycelekli
- @xixi-box
Artifacts
- Images:
opensandbox/<component>:release-1.3.0-rc.1(Docker Hub / GHCR / ACR)
Installation
# Platform (Kubernetes) — render the chart at this tag and apply
git clone https://github.com/opensandbox-group/OpenSandbox
cd OpenSandbox
git checkout release-1.3.0-rc.1
helm dependency build manifests/charts/opensandbox # package file:// sub-charts (not committed)
helm template ./manifests/charts/opensandbox | kubectl apply -f -
# or point your GitOps platform (Argo / Flux) at the repo path + tag
Verify what you installed against the BOM: see Release Verification.