Share feedback
Answers are generated based on the documentation.

sbx policy reset

DescriptionReset policies to defaults
Usagesbx policy reset [flags]

Description

Remove all custom policies and restart the daemon to restore defaults.

This deletes the local policy store and restarts the daemon immediately. You are then prompted to choose the global network policy; without an interactive terminal, initialize it after the reset by choosing a preset as shown below.

If sandboxes are currently running, they will be stopped when the daemon shuts down. You will be prompted for confirmation unless --force is used.

With --cloud, deletes the custom cloud network policy for your account and leaves the local daemon alone. You will be prompted for confirmation unless --force is used. Afterwards the default the server now stores is printed.

Options

OptionDefaultDescription
-f, --forceSkip confirmation prompt

Global options

OptionDefaultDescription
--cloudDispatch to Docker Cloud Sandboxes API instead of local sandboxd (supported by a growing set of verbs — run 'sbx --cloud --help' for the current list)
-D, --debugEnable debug logging
--no-inputNever prompt; commands that need an answer fail with the command to run instead

Examples

# Reset policies — prompts if sandboxes are running
sbx policy reset

# Reset policies without confirmation
sbx policy reset --force

# Reset and initialize in a script; use balanced, allow-all, or deny-all
sbx --no-input policy reset --force && sbx policy init balanced