Repository navigation
Description
Parent
What to build
An operator on a host that refuses namespaces, such as ECS Fargate, sets worker_sandbox to "filter", and the Gateway starts and serves grants. With "filter", the supervisor launches each grant worker directly: no bubblewrap, a cleared environment, and only the control socket and standard streams open. The grant worker then applies the base layers from the previous ticket. With the field omitted, or set to "namespaces", behaviour is as before. The Gateway never falls back from one sandbox to the other.
When the chosen sandbox can't start, startup exits with worker sandbox "<sandbox>" failed: <layer>: <cause>. The error points to the operator guide's section on choosing a worker sandbox and never suggests the other value.
CI proves the filter sandbox under the same restriction Fargate imposes: a new job runs the real Gateway in a container under Docker's default security profile.
Acceptance criteria
- The Gateway configuration accepts optional
worker_sandboxwith values"namespaces"(the default when omitted) and"filter". Any other value fails configuration loading - Under
"filter", grant workers start without bubblewrap and without needing/usr/bin/bwrap, in both sidecar and shared mode - There is no automatic fallback in either direction
- A startup failure exits non-zero with an error naming the sandbox and the failed layer, pointing to the operator guide, and not suggesting the other sandbox
- A new CI job, inside a container under Docker's default security profile, runs the runtime test under
"filter"(sidecar and shared mode, concurrent users, cutoff, revocation) - The same job runs the worker sandbox containment test
- The same job proves that
"namespaces"fails at startup there with the named error - The configuration reference documents
worker_sandboxand both values - The operator guide has a section on choosing a worker sandbox: the namespace sandbox is recommended, the filter sandbox is for hosts that can't create namespaces and gives up the namespace layer, and the supervisor stays unprivileged in both
- The troubleshooting row for a worker sandbox startup error covers both sandboxes
- The design record's platform line names both worker sandboxes
Decided in: #21 (spec); ADR 0001; the probe and research on prototype/18-isolation-probe
Live step at merge: none
Activity
feat(gateway): Every grant worker confines itself before it reads any…
fix(gateway): A confined grant worker cannot start a process by clone3 (