gVisor

Prod is Down: Free gVisor-Based Simulator Gives Strangers Root Access for Realistic Linux Incident Training

A Russian systems administrator has launched Prod is Down, a free online platform that lets users practice real incident response by granting them root consoles on deliberately broken Linux servers. The tool currently offers 13 scenarios covering PostgreSQL failures, OOM Killer events, full disks, expired certificates, nginx 502 errors, inode exhaustion, DNS issues, and open file limits. Each exercise runs inside gVisor sandboxes with strict resource limits, internal-only networking, and automated verification that checks service health rather than player commands. The author implemented an emulated systemd in Python so trainees can use familiar systemctl and journalctl commands without running a real init system. Multiple layers of isolation, including overlay filesystem tweaks and size monitoring, prevent abuse while still allowing sudo and realistic debugging. The platform records three random variants per scenario so memorized fixes from previous runs do not work on subsequent attempts.

Do Sandbox Restrictions Actually Work for AI Agents Running in Linux and gVisor?

An in-depth technical analysis examines whether security mechanisms such as Landlock, classic BPF socket filters, and CGROUP_DEVICE programs enforce intended restrictions inside container and VM-based sandboxes used by AI agents. Tests conducted on Linux 6.8 and two gVisor releases (20260817.0 and 20260831.0) revealed that Landlock calls consistently return ENOSYS inside gVisor, rendering the mechanism unavailable. CGROUP_DEVICE programs could be loaded and attached successfully under elevated capabilities, yet they produced no observable effect on device access. Classic BPF filters attached via SO_ATTACH_FILTER were accepted without error even with zero capabilities, but continued to allow UDP datagrams that should have been dropped. The study emphasizes that successful configuration alone does not guarantee enforcement and outlines a verification workflow that must be repeated for each target environment, runtime, and policy change before deploying restricted AI tools.

Do You Really Know What Your AI Agent Is Doing in the Sandbox?

The rise of agentic AI systems has exposed critical gaps in observability when agents run inside strong isolation environments. Traditional eBPF-based monitoring on the host kernel fails when agents execute under separate kernels provided by gVisor, Kata, or Firecracker. Experiments with a controlled syscall generator show that visibility depends heavily on filesystem configuration rather than the choice of runtime. Standards such as MCP, OpenTelemetry, and RuntimeClass address parts of the agent lifecycle but leave actual syscall-level reporting undefined. Measurements across multiple configurations reveal that some operations, especially execve, never reach the host regardless of the sandbox used. The findings highlight that security tooling must be re-evaluated after every change in sandbox settings.