Craig Osterhout
bf47d790ad
<!--Delete sections as needed --> ## Description Update governance docs for local deny rules. - Clarified that local deny rules are evaluated under org governance and layer on top of org policy. Only allow rules are inactive. - Added examples of the `--deny-network` flag (new in v0.38) on `sbx create` and `sbx run`, which sets per-sandbox deny rules at creation time. https://deploy-preview-25714--docsdocker.netlify.app/ai/sandboxes/governance/ ## Related issues or tickets https://docker.slack.com/archives/C097C5LRXFF/p1785455753455409 ## Reviews <!-- Notes for reviewers here --> <!-- List applicable reviews (optionally @tag reviewers) --> - [ ] Technical review - [ ] Editorial review - [ ] Product review --------- Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
2.1 KiB
title, linkTitle, weight, description, keywords
| title | linkTitle | weight | description | keywords |
|---|---|---|---|---|
| Filesystem access policies | Filesystem access | 40 | Control which host paths Docker Sandboxes can mount as workspaces with organization filesystem policies. | docker sandboxes, filesystem access, filesystem rules, workspace mount, organization policy, governance |
Filesystem access policies control which host paths a sandbox can mount as a workspace. Each policy contains one or more rules that restrict sandbox workspaces to approved directories.
Filesystem access is managed with organization policies. When
organization governance is active, organization rules determine which paths a
sandbox can mount, and the local filesystem allow rules from the default preset
become inactive. sbx policy deny applies to network access only, so there are
no local filesystem deny rules to layer on top. See
Precedence.
Rule syntax
Filesystem rules use the actions read and write. Resources are host path
patterns.
A writable workspace mount must be allowed by both a read rule and a write
rule. A read-only workspace needs only read.
Examples:
~/**/data/project/**C:\data\project\**\\wsl.localhost\<distro>\data\project\**
Use ** to match a directory tree recursively. A single * matches only one
path segment. For exact path matching behavior across macOS, Linux, Windows,
and WSL, see Filesystem rules.
Organization filesystem rules
Organization filesystem rules belong to policies that can apply to the whole organization or to selected teams. For setup steps and team scoping, see Organization policies.
Filesystem policy is checked when a workspace is mounted, which happens when a sandbox is created. To apply a filesystem policy change to a running workflow, remove the sandbox and create a new one.
Troubleshooting
Sandbox cannot mount workspace
If a sandbox fails to mount with a mount policy denied error, verify that the
filesystem allow rule uses ** rather than *. A single * doesn't match
across directory separators.