What exact operations, authentication, validation, privilege, runtime, image, mount, resource-limit, network-policy, and cleanup rules belong to the restricted supervisor for both supported Linux topologies? Define the protocol and trust boundary narrowly enough that Paseo and sandboxed agents never receive a general Docker or containerd control surface. Also settle the host service installation/upgrade boundary, workspace-root registration, Docker socket/GID/deployment mapping, and operator workflow required to activate the supervisor in each topology.
Part of #1
Blocked by: #2
## Question
What exact operations, authentication, validation, privilege, runtime, image, mount, resource-limit, network-policy, and cleanup rules belong to the restricted supervisor for both supported Linux topologies? Define the protocol and trust boundary narrowly enough that Paseo and sandboxed agents never receive a general Docker or containerd control surface. Also settle the host service installation/upgrade boundary, workspace-root registration, Docker socket/GID/deployment mapping, and operator workflow required to activate the supervisor in each topology.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #1
Blocked by: #2
Question
What exact operations, authentication, validation, privilege, runtime, image, mount, resource-limit, network-policy, and cleanup rules belong to the restricted supervisor for both supported Linux topologies? Define the protocol and trust boundary narrowly enough that Paseo and sandboxed agents never receive a general Docker or containerd control surface. Also settle the host service installation/upgrade boundary, workspace-root registration, Docker socket/GID/deployment mapping, and operator workflow required to activate the supervisor in each topology.