Let's talk a little about sbx

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61

# Let's talk a little about `sbx`

## Why you should use `sbx`

![sbx security model](./assets/sbx-security-model.drawio.svg)

## Prerequisites

- **You need a Docker Account for using SBX**
- You need Docker Desktop (only for [../07-play-lego-with-kits/README.md](../07-play-lego-with-kits/README.md))


## Install `sbx`

Start by installing `sbx` by following these instructions: [https://docs.docker.com/ai/sandboxes/install/](https://docs.docker.com/ai/sandboxes/install/)

If you haven't chosen a default preset, the CLI prompts you before it runs a sandbox. Running `sbx policy reset` clears the preset and prompts you to choose again:

```raw
Initialize the global network policy for your sandboxes:

  Applies to all sandboxes, current and future — change it later with
  "sbx policy allow/deny/rm". Kits, including built-in agent kits, may
  also add per-sandbox rules.

     1. Open         - All network traffic allowed, no restrictions.
     2. Balanced     - Default deny, with common dev sites allowed.
     3. Locked Down  - All network traffic blocked unless you allow it.

  Use ↑/↓or 1-3 to navigate, Enter to confirm, Esc to cancel.
```

## Test your installation - First contact with `sbx`

In the current folder, run the following command:

```bash
sbx run shell .
```

Then try these commands:
```bash
uname
go version
node --version
cargo --version
```

In another terminal, type:
```bash
sbx ls
```

Then:
```bash
sbx
```

Stop and destroy your sandbox.

**It is time to get serious**.