Upgrade to sysbox 0.7.1 - #177
Open
okcleary wants to merge 1 commit into
Open
Conversation
Fixes nestybox/sysbox#998, a deadlock in sysbox-fs's zombie reaper that can occur when many Docker containers are started/stopped concurrently inside a Sysbox container. The FUSE handler and the reaper goroutine could each hold the other's lock indefinitely, wedging the affected container and any other Sysbox container on the same host. Fixed upstream via nestybox/sysbox-fs#119 and coder#121. SHA256 checksums for the v0.7.1 .deb packages were downloaded from https://downloads.nestybox.com/sysbox/releases/v0.7.1/ and verified against the published release notes before being applied here. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
sysbox 0.7.1 (released 2026-07-31) fixes nestybox/sysbox#998: a deadlock in sysbox-fs's zombie reaper that can occur when many Docker containers are started/stopped concurrently inside a Sysbox container. Per the release notes:
The deadlock wedges the affected Sysbox container and, per the issue report, also hangs other Sysbox containers on the same host (
docker run --runtime=sysbox-runcblocks indefinitely) untilsysboxis restarted. It's fixed upstream in sysbox-fs via nestybox/sysbox-fs#119 (TryLockin the reaper to avoid blocking new FUSE handlers behind a pending writer lock) and nestybox/sysbox-fs#121 (replace synchronous child-process waits with async reaping so the reaper's lock isn't held indefinitely on a slownsenterexit).Checksum provenance
Downloaded both
.debpackages directly from the official release URLs and verified locally before use:Both match the checksums published in the sysbox v0.7.1 GitHub release notes.
Shape
Follows the same three-file pattern as #163 (and #145 before it) for a sysbox version bump, updated for the current layout where the SHA lives in
scripts/sysbox_sha.sh(added in #171) rather than theMakefile:deploy/Dockerfile: bumpSYSBOX_VERSION0.7.0->0.7.1scripts/sysbox_sha.sh: bump both arch checksums.github/workflows/release.yaml: bump the matchingshavalues in the release build matrix (this file still carries its own copy of the checksums alongside the script)No other files reference the pinned version or checksums.
Testing
Built the image locally on native arm64 (
make -j ARCH=linux/arm64 build/image/envbox) as a smoke test — sysbox-ce 0.7.1 downloads, its checksum verifies, and it installs cleanly in the image;envboxbinary runs. Didn't attempt cross-arch (amd64) build locally; CI's release matrix builds both natively.