Clarify Omarchy update free-space errors in the guest - #107
Open
Fail-Safe wants to merge 1 commit into
Open
Conversation
Omarchy's 10 GiB check measures the VM root disk, but the stock message reads like a Mac free-space failure. Explain the guest boundary and show df -h / when Try Omarchy's build spec is present.
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
1 participant
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.
Summary
omarchy-update-requires-free-spaceso low-disk update failures explain that the 10 GiB requirement is inside the Omarchy VM disk, not on the Macdf -h /and a short cleanup hint when/usr/share/try-omarchy/build-spec.jsonis presentFixes #93
Problem
Reporters see
You need at least 10 GiB free to safely update Omarchy.and assume it refers to Mac free space. Try Omarchy's working disk is 24 GiB; after normal use, guestdfavail can fall under 10 GiB while the Mac still has plenty of free space.Approach
Reviewed authenticity backport of the pinned upstream helper. Behavior is identical outside Try Omarchy guests. Durable capacity relief remains #104.
Test plan
python3 -m unittest discover -s guest/tests -p 'test_*.py'python3 guest/tests/verify.py --source <pinned Omarchy 4.0.2 checkout>< 10 GiBfree on/, runomarchy updateand confirm the clarifying lines anddf -h /appearOMARCHY_UPDATE_FORCE=1still skips the check