---
name: "gvisor-sandboxed-container-runtime"
description: "Isolate multi-tenant and untrusted container workloads using Google gVisor user-space kernel."
metadata:
  author: "Google"
  version: "1.0.0"
  runtime_compatibility:
    - "codex"
    - "claude-code"
    - "cursor"
    - "windsurf"
triggers:
  - "setup runsc containerd"
  - "configure gvisor runtimeclass k8s"
  - "sandbox untrusted container execution"
permissions:
  fs_read: true
  fs_write: "workspace"
  shell_exec: false
  net_access: false
---

# gVisor Secure Kernel Sandboxing for Untrusted Code

Configures Google gVisor (runsc): intercepting Linux syscalls in user space, configuring Sentry application kernel, Gofer file system proxy, integration with containerd and Kubernetes RuntimeClass.

## When to Invoke
Invoke this skill whenever you need to:
- setup runsc containerd
- configure gvisor runtimeclass k8s
- sandbox untrusted container execution

## Execution SOP & Rules
1. Install runsc and register runtime with containerd: runsc install.
2. Configure containerd /etc/containerd/config.toml under plugins.'io.containerd.grpc.v1.cri'.containerd.runtimes.runsc.
3. Create K8s RuntimeClass: apiVersion: node.k8s.io/v1, kind: RuntimeClass, handler: runsc.
4. Specify runtimeClassName: runsc in pod spec to enforce kernel sandbox boundaries.

## Verification Checklist
- Run local linting, syntax validation, and type-checks before reporting completion.
- Ensure all created or modified files adhere to workspace boundaries and avoid uncommitted secrets.
- Verify tests or build commands exit cleanly with return code 0.