Shipped · DevOps and infrastructure

What google/gvisor shipped

The public repository of Gvisor · github.com/google/gvisor

Written by FoxPlug from the repository's own releases; not affiliated with Gvisor. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/google/gvisor; Gvisor did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.

Get a weekly update like this for your product, free

Or Use it as a GitHub Action

Follow gvisor's weekly shipped digest

Week of October 5, 2026

What shipped

Why it matters

This week tightened core networking behavior: accepted connections keep the congestion control chosen on the listener, and both Reno and CUBIC now account for ACK credit correctly, which affects throughput and recovery timing for TCP workloads. The sandbox also became more resilient to cgroup freezer operations on systrap, and procfs gained the system-wide file count that tools read. The 20261005.0 release packages these and earlier changes for users installing from apt or the release bucket.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

Accepted TCP endpoints now inherit the listener's congestion control. Reno and CUBIC keep ACK credit straight. EROFS reads no longer stop at the inline tail. systrap survives cgroup freezer cycles. /proc/sys/fs/file-nr works. gVisor 20261005.0 is out.

Post for LinkedIn

This week's gVisor changes focus on networking correctness and sandbox resilience. Accepted TCP endpoints now inherit the congestion control algorithm selected on the listener, including SYN-cookie handshakes. Reno consumes ACK credit before growing its congestion window, and CUBIC preserves growth credit so windows grow at the right rate after fast recovery. EROFS reads that span full blocks and tail-packed inline data now return the complete requested range, and oversized exec arguments return E2BIG as on Linux. On systrap, the seccomp notify path retries on ENOENT so freezing and thawing with the cgroup v2 freezer no longer kills the application. procfs also gained /proc/sys/fs/file-nr and file-max, and /proc/[pid]/stat reports PF_EXITING. Release 20261005.0 is available.

Week of September 28, 2026

What shipped

Why it matters

This week addresses correctness in signal handling, container cleanup, and filesystem permissions to better match Linux behavior. Infrastructure improvements for lock checking and cgroup compatibility make gVisor more reliable for production workloads that depend on precise seccomp and resource management semantics.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

GVisor 20260928.0 released: MASQUERADE target for netfilter, SECCOMP_RET_KILL_PROCESS fix, improved cgroup cleanup, and enhanced lock contract enforcement.

Post for LinkedIn

GVisor 20260928.0 is now available. This release includes the iptables MASQUERADE target with strict validation, a critical fix for SECCOMP_RET_KILL_PROCESS handling, improved container creation cleanup, and enhanced lock contract checking across package boundaries. These changes improve compatibility with Linux behavior and system reliability.

Week of September 21, 2026

What shipped

Why it matters

This week covers correctness fixes for system call tracing and capability enforcement, new netfilter and nftables features for packet processing, signal mask visibility in process status, and performance improvements on the syscall path. These changes improve container isolation semantics, debugging capabilities, and runtime performance.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

GVisor 20260921.0 ships with strace thread tracking, iptables comment matches, /proc signal masks, user namespace limits, and 2-4% syscall speedup via lock-free forwarder.

Post for LinkedIn

GVisor 20260921.0 improves system call debugging with per-thread strace events, adds netfilter comment match extension and nftables checksum validation, exposes signal masks in /proc/[pid]/status, enforces /proc/sys/user/max_user_namespaces limits, fixes file capabilities under no_new_privs to match Linux, and makes the interrupt forwarder lock-free for 2-4% syscall latency reduction.

Week of September 14, 2026

What shipped

Why it matters

Release 20260914.0 brings significant compatibility improvements, particularly for systemd integration and GPU support. Performance optimizations in seccomp and fixes to file handling make gVisor more practical for real-world workloads requiring large files and complex socket operations.

Changelog entry

Example posts FoxPlug drafted from these changes. Not written or posted by the project.

Post for X

GVisor 20260914.0 is out. Better FUSE file support, systemd compatibility, GPU restoration, and seccomp performance improvements.

Post for LinkedIn

GVisor 20260914.0 released with major improvements: FUSE now handles files >2GB, seccomp initialization 8ms faster per sandbox, systemd 60+ compatibility via STATX_ATTR_MOUNT_ROOT, GPU device restoration fixes, and socket options up to 1MB. Check the changelog for full details.

Weeks with too little public activity are left out rather than filled in. Last updated 2026-10-13.

Is this your repo? Ask us to remove this page.