You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 2026bdc
Browse filesBrowse the repository at this point in the historyBrowse files
fix(docker): launch the admitted agent spec and harden the notify boundary
- Deliver the driver's real main-process spec via OPENSHELL_MAIN_PROCESS_SPEC
instead of a hardcoded placeholder shell loop, so the sandbox command and
tty semantics reach the Docker workload container.
- Move the topology payload (which carries the boundary listener token) out
of world-readable argv into a driver-owned 0600 file.
- Deliver the admitted isolation backend on the driver-owned
OPENSHELL_ADMITTED_ISOLATION_BACKEND channel.
- Gate the host-supervisor spawn path as Linux-only with a fail-closed stub
so the driver compiles on non-Linux gateways again.
- Re-validate seccomp notification liveness (SECCOMP_IOCTL_NOTIF_ID_VALID)
after every pid-derived read, so a recycled PID cannot attach another
process's identity or memory to a mediated connection.
- Bound the retained pending-socket map so a socket()/close() loop cannot
exhaust host supervisor descriptors; eviction fails closed against the
container's disabled network.
- Restore Docker default-profile parity for escape-relevant syscalls with an
explicit EPERM deny group on top of the notify profile.
- Enable TCP_NODELAY on the injected mediation socket pair.
- Document host_gateway_ip and the Unsupported error in RFC 0012; drop the
unrelated sccache configuration change.
Signed-off-by: Drew Newberry <anewberry@nvidia.com>
`Invalid` covers descriptor, version, and backend mismatches; `Denied` covers authenticated attachment rejection; `Unavailable` covers transient inability to serve an operation; `Failed` covers other backend faults; and `Terminated` reports boundary or workload termination, or an operation against an inactive boundary. An error never advances the lifecycle or authorizes an operation, and backend selection never falls back.
337
347
348
+
An `Unsupported` error variant reports that the selected backend does not implement an optional contract operation; it maps to the `Unavailable` kind for status purposes and never weakens a mandatory conformance requirement.
349
+
338
350
A backend may retry backend-private work within one `attach` call. The supervisor calls `attach` at most once per orchestration attempt. Attach-time establishment uses sandbox identity and launch generation as an idempotency key. If the operation does not return `Bound`, the compute driver reclaims the topology rather than reusing an ambiguous resource.
0 commit comments