Repository navigation
Run the published kits from a dedicated folder - #15
Merged
Merged
Conversation
sbx refuses to mount the home directory as the workspace, because it overlaps the Sandboxes configuration, state and credentials. The README now starts the published kits from an empty ~/sbx-lab folder and gives the run command for each of them (the built-in lab, hello-lab and building-images). The built-in lab's pages say the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The folder sbx run starts from is mounted into the sandbox, so starting from the home directory would expose keys, credentials and other projects to it. That, not the sbx refusal, is the reason to use an empty folder. Co-Authored-By: Claude Opus 5.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.
Feedback: running the published-kit command from the home directory fails with
mount "/Users/<me>" overlaps Sandboxes configuration, state or credentials. It works from a dedicated folder (mkdir ~/sbx-lab && cd ~/sbx-lab).The guidance is framed as a security practice:
sbx runmounts the folder it starts from into the sandbox, read-write, so starting from the home directory would expose SSH keys, cloud and registry credentials, shell history and other projects to it. A content kit doesn't use the workspace, so an empty folder is all a lab needs. Thesbxerror is mentioned as a side note.README.md, published kits section: the why, thenmkdir -p ~/sbx-lab && cd ~/sbx-lab, then one run command per kit:-p 8085:8085)hello-lab(-p 8085:8085 -p 3000:3000)building-images(-p 8085:8085 -p 5050:5050)README.md: the local content-kit example says "from the repo root" instead of "from any folder", and the open point about the mounted workspace says never to start from the home directory.03-content-kit.md,04-one-reference.md): start from a dedicated, empty folder, never the home directory, with the same reason.Not run end to end; the commands use the published
0.1.4references.🤖 Generated with Claude Code