docs(hub): document the rootfs sidecar so publishers don't reproduce #242#253
Merged
Conversation
…242 HUB.md's "Publishing a new pack" walked through pack → release → registry but never mentioned the rootfs sidecar — so anyone following it would upload only the .tar.zst and ship a pack that's un-restorable on any host but their own (the exact #242 bug). Now documents: from-image rootfs lives outside the snapshot dir and ships as a content-addressed <sha>.rootfs.zst sidecar; upload BOTH files to the same release; pull derives the sidecar URL as the pack's sibling and caches by sha. Pack-format section updated to match (rootfs.ext4 is only in-tar when the rootfs is inside the snap dir). Co-Authored-By: Claude Opus 4.8 (1M context) <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
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.
Doc-debt from #242/#247. HUB.md's publish guide never mentioned the rootfs sidecar — anyone following it would upload only the .tar.zst and ship an un-restorable-cross-host pack (the exact bug #242 fixed). Now: pack format notes the content-addressed
<sha>.rootfs.zstsidecar; the publish steps upload BOTH files to the same release; explains pull derives the sidecar as the pack URL's sibling + caches by sha.🤖 Generated with Claude Code