Blog

Feed 

The anatomy of a 3B step

By Shayon Mukherjee on 19 November 2026

This article was contributed by Tines. Shayon Mukherjee is an engineer at Tines, working on the runtime infrastructure behind 3B. It was originally published on Tines Notebook.

At Tines we’re building 3B, where people work with an agent to automate enterprise software. Workflows, internal apps, and agents are all made of steps, each a directory with a Dockerfile and a program that reads stdin and writes stdout. The result becomes the input to whatever runs next.

Each run gets a fresh Linux sandbox, including a fresh gVisor application kernel, which we delete afterwards because we have to treat the program as untrusted even if it appears to have worked. That means its image and persistent files have to survive outside the environment we throw away.

Read more »

Blink and it's back: how gVisor checkpoint/restore got 5x faster

By Jing Chen, Ayush Ranjan, Jamie Liu and Shayon Mukherjee on 12 November 2026

A running gVisor sandbox is saved with runsc checkpoint to snapshot files (checkpoint.img, pages_meta.img, pages.img and fs/), on local disk or in a GCS bucket, and restored with runsc restore into the same sandbox anywhere, any time later. Restoring a 2 GiB sandbox takes 939 ms from disk and 71 ms from the page cache.

runsc checkpoint saves the full state of a gVisor sandbox to files: every process, every open file, every socket, and the application’s memory. runsc restore brings it back, on the same machine or on a different one, and the applications continue as if nothing happened.

This feature is not new. gVisor could checkpoint a sandbox in 2018. But the 2018 version was slow, and some people still think of gVisor checkpoint/restore that way. A lot changed in the last few years. In our tests below, restoring a 2 GiB sandbox from a slow disk went from 5,106 ms to 939 ms, about 5 times faster, saturating the max speed of the disk. When the image is already in the host page cache, it went from 651 ms to 71 ms.

Read more »

gVisor is being donated to CNCF

By Etienne Perot and Jing Chen on 02 October 2026

gVisor being donated to the Cloud Native Computing Foundation, a subsidiary of the Linux Foundation.


In 2018, Google open-sourced gVisor under the Apache 2.0 license. To the best of its contributors’ knowledge, it has ever since remained the second most mature implementation of Linux, after Linux.

This year, the gVisor project is being donated to CNCF, and its governance model is shifting accordingly.

Read more »

Who needs VMs? Run systemd and full Linux desktop apps in gVisor

By Ryan El Kochta and Shailend Chand on 17 September 2026

GNOME running under systemd in gVisor, with the gvisor.dev website, uname showing 4.19.0-gvisor, and the status of the nginx service all visible.

As an OCI runtime, gVisor is traditionally used to sandbox application containers containing a single service. These containers have little to no userspace running in them except the service itself. While this is great for efficiency and scalability, there are some use cases that can benefit from having something closer to a full Linux system inside the sandbox, with a “normal” service manager and system daemons.

gVisor now has gained support for running systemd. To this end, support for a handful of major new kernel APIs has been added to gVisor, including:

along with numerous smaller features and bug fixes.

Systemd has been tested to work in full-system gVisor containers with Ubuntu, Debian, and Red Hat’s Universal Base Images.

Read more »

Scaling Agentic-RL Sandboxes to the Millions with gVisor at Tencent

By Yifeng Tan, Hua Liu and Hui Chen on 23 April 2026

This article was contributed by Tencent. Yifeng Tan, Hua Liu, and Hui Chen are engineers at Tencent, responsible for the internal container infrastructure.

As LLMs evolve from chat interfaces to autonomous agents, building a robust and secure isolation environment becomes a necessity. We chose gVisor as the default sandbox for our Agentic-RL scenarios. Today, we run millions of gVisor sandboxes daily for Agentic-RL training in production, and that scale continues to grow. After more than 74,000 side-by-side comparisons between runsc (gVisor) and runc (unsandboxed/Linux), combined with targeted fixes driven by real-world workloads, we have essentially closed the execution correctness gap with runc, fully meeting our production-grade business requirements. During this process, we successfully investigated and resolved gVisor compatibility issues that accounted for approximately 1.7% of all test cases.

This post focuses on CPU-centric code execution and testing workloads. We will discuss gVisor compatibility verification and highlight representative issues, skipping implementation details like GPU support, image distribution, or cluster scheduling. We aim to answer three questions:

  1. Why choose gVisor?
  2. Why doesn’t manual compatibility verification scale?
  3. How can AI agents analyze compatibility issues, what do typical failures look like, and what best practices have we established?

Read more »


If you would like to contribute to the gVisor blog check out the instructions.