Skip to content

docs: explain Linux sandbox prerequisites #188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shadaj merged 1 commit into from
Nov 5, 2026
Merged

docs: explain Linux sandbox prerequisites #188

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/docs/infinity-code/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,18 @@ infinity provider install bedrock --crate infinity-provider-bedrock
infinity rap install --user --crate sandbox-local
```

On Linux, `sandbox-local` uses Bubblewrap (`bwrap`). Install the system package before installing the RAP server. If `bwrap` is missing, the build script attempts to build it from source and requires Git, a C compiler, and the `libcap` development headers. For example:

```bash
# Debian / Ubuntu
sudo apt install bubblewrap build-essential libcap-dev

# Fedora / Amazon Linux 2023
sudo dnf install bubblewrap gcc libcap-devel
```

On macOS, the sandbox uses `sandbox-exec` and does not require Bubblewrap.

[Model providers](./model-providers.md) run as separate processes managed by the daemon and are registered in `~/.infinity/providers.json`; at least one must be installed. The Bedrock provider uses your ambient AWS configuration (e.g. `AWS_PROFILE` or environment credentials).

To update later:
Expand Down
Loading