mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-10-11 03:40:05 +00:00
0b562dadb6
Fabro-Run: 01KS9BXFGAZ32SGNRE4YJV1354
Fabro-Completed: 7
Fabro-Checkpoint: e2b2831ff6
⚒️ Generated with [Fabro](https://fabro.sh)
16 lines
1 KiB
Text
16 lines
1 KiB
Text
---
|
|
title: "Sandboxing"
|
|
description: "Sandboxing workflow execution"
|
|
---
|
|
|
|
Sandboxes isolate agent execution from the host machine. When an agent runs a shell command, edits a file, or searches code, it does so inside a sandbox — preventing unintended side effects on the host and providing a reproducible environment for each run.
|
|
|
|
Fabro supports three sandbox providers: `local` (no isolation), `docker` (container-level), and `daytona` (cloud VM). See [Environments](/execution/environments) for full provider-specific configuration.
|
|
|
|
## Network access control
|
|
|
|
For cloud sandboxes (Daytona), you can control outbound network access with `[environments.<slug>.network]`. Three modes are available: `"allow_all"` (default), `"block"`, and `"cidr_allow_list"` with an `allow = ["..."]` CIDR list.
|
|
|
|
Server defaults in `settings.toml` apply when a run config doesn't specify `network`. Individual run configs can override the server default.
|
|
|
|
See [Environments — Network access](/execution/environments#network-access) for syntax examples and the full reference.
|