Repository navigation
gVisor sandboxes move to release 20261019.0 from the 2026-10-17 nightly - #3177
Merged
Dmitry Berkovich (dberkov) merged 2 commits intoOct 23, 2026
Merged
Dmitry Berkovich (dberkov) merged 2 commits into
Dmitry Berkovich (dberkov) merged 2 commits into
Conversation
The 2026-10-17 nightly was pinned for google/gvisor@b79256080dec, the multiple filesystem checkpoint bundles. Release 20261019.0 is the first tagged release that carries it. Version v4 stays so a memory snapshot taken under it still restores.
Collaborator
|
nybidari - could you please verify that this is a right version that includes rootfs and no-pause feature |
nybidari
approved these changes
Oct 23, 2026
Collaborator
|
Yes, this release includes both features. |
Every worker fetches every enabled version. A snapshot taken under the nightly cold boots on its next resume, keeping its files.
Collaborator
Author
|
Dmitry Berkovich (@dberkov) nybidari fixed the nit (dropped v4). PTAL |
nybidari
approved these changes
Oct 23, 2026
Dmitry Berkovich (dberkov)
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The shipped gVisor config pinned the 2026-10-17 nightly for google/gvisor@b79256080dec, which saves and restores multiple filesystem checkpoint bundles. Release 20261019.0 is the first tagged release that contains it, so the config can point at a release again.
Change.
manifests/ate-install/sandboxconfig-gvisor.yamlreplacesv4withv5, release 20261019.0 for amd64 and arm64, asdefaultVersion, the way the previous bumps did.docs/api-guide.mdmirrors it. The sha256 values come from the downloaded tarballs, which match the published.sha512files.Breaking change. A MEMORY snapshot taken under
v4cold boots on its next resume: it keeps its files and loses its memory state. Recut golden snapshots after upgrading. Please add thebreaking-changelabel.Tests.
go test ./api/infra/k8s/ate/v1/applies the edited manifest against the CRD and the admission policy;./cmd/ate-setup/...and./cmd/atelet/pass. CI's e2e lanes install this manifest and boot, suspend and restore gVisor actors on it.AI use: AI-assisted, I reviewed and tested it.