nprasad2077/docker-docs
1
0 Fork 0
mirror of https://github.com/docker/docs.git synced 2026-11-04 10:01:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: use policy refresh for stale governance rules

Browse Source 
Monitoring guidance recommended resetting policy to fetch changes. Use the refresh command and explain how it affects new and existing connections.
This commit is contained in:
David Karlsson committed 2026-10-21 11:09:42 +00:00
1 parent e57dbfef9e
commit 114c744d24
1 file changed
+7 -4
Download Patch File Download Diff File Expand all files Collapse all files
content/manuals/ai/sandboxes/governance/monitor-and-enforce/monitoring.md
+7 -4
View File
@@ -83,10 +83,13 @@ default network org all network: 38 allow, 4 deny
```
`Governance` shows which organization manages the policy, and `Sync` confirms
the daemon has pulled the latest rules. If the sync state shows an error or a
stale timestamp, the daemon may not have the most recent org policy. Run
`sbx policy reset` to force a fresh pull. `Hidden` reports how many inactive
rules are suppressed and how to reveal them.
the daemon has pulled the latest rules. `Hidden` reports how many inactive rules
are suppressed and how to reveal them.
If the sync state shows an error or a stale timestamp, run `sbx policy refresh`
to fetch and apply the latest policy without restarting the daemon or stopping
sandboxes. The policy applies to new connections. To close existing connections
that the updated policy denies, restart the sandbox.
If Docker can't determine which organization governs your account, policy
output shows `Governance: Unresolved`, and the dashboard shows the same