Profiles that need raw network run on a non-sandboxed runtime alongside OpenShell #1971

Open
opened 2026-11-13 16:54:09 +00:00 by sam · 0 comments
Owner

OpenShell policy cannot express raw DNS, UDP or ICMP, so profiles that need them (the firewall investigator and similar) cannot run sandboxed. Decision: keep them, on a non-sandboxed runtime.

Today the runtime is one global setting (containers.runtime). Add a per-profile runtime choice so a profile can opt out of the sandbox while the rest of the instance runs on OpenShell. The daemon keeps a non-sandboxed backend behind daemon.TaskRuntime for those profiles, which the retirement of the relay, proxy and sandbox networks must leave in place.

Done when, on an instance whose runtime is openshell, a profile marked non-sandboxed runs its task with raw network access, every other profile still runs in OpenShell, and the choice is edited through the control plane (API and dashboard).

OpenShell policy cannot express raw DNS, UDP or ICMP, so profiles that need them (the firewall investigator and similar) cannot run sandboxed. Decision: keep them, on a non-sandboxed runtime. Today the runtime is one global setting (containers.runtime). Add a per-profile runtime choice so a profile can opt out of the sandbox while the rest of the instance runs on OpenShell. The daemon keeps a non-sandboxed backend behind daemon.TaskRuntime for those profiles, which the retirement of the relay, proxy and sandbox networks must leave in place. Done when, on an instance whose runtime is openshell, a profile marked non-sandboxed runs its task with raw network access, every other profile still runs in OpenShell, and the choice is edited through the control plane (API and dashboard).
sam added the featurehigh labels 2026-11-13 16:54:14 +00:00
sam added the deferred label 2026-11-15 17:26:08 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1971