docs: document allowNetworkMounts option for directory watching#255
Conversation
Add a "Watching network filesystem mounts" section to the watch docs covering the allowNetworkMounts / allow_network_mounts opt-in, the envd v0.6.4 requirement, and the caveat that changes from clients outside the sandbox are not propagated to the watcher. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PR SummaryLow Risk Overview In the new Python example, Reviewed by Cursor Bugbot for commit aea5f3e. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
| import { Sandbox } from 'e2b' | ||
|
|
||
| const sandbox = await Sandbox.create() | ||
| const dirname = '/mnt/nfs-share/my-dir' |
There was a problem hiding this comment.
What would happen if the watchDir gets called on '/mnt' with recursive: true but no allowNetworkMounts: true ?
There was a problem hiding this comment.
the precondition for watching anything on the network mount is allowNetworkMounts
if you don't have this enabled, no matter what else is passed will cause an error
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2 participants
Documents the new
allowNetworkMounts/allow_network_mountsoption for filesystem directory watching (e2b-dev/E2B#1420). Adds a "Watching network filesystem mounts" section todocs/filesystem/watch.mdxwith JS and Python examples, the envdv0.6.4requirement, and a note that events on network mounts may be unreliable. Per the request, it also calls out that changes made by another client outside the sandbox are not propagated to the watcher.🤖 Generated with Claude Code