Skip to main content
This page documents legacy OpenHands V0 behavior. For the current V1 sandbox model, see Custom Sandbox (V1).
These settings are only available in Local GUI. OpenHands Cloud uses managed sandbox environments.
The sandbox is where the agent performs its tasks. Instead of running commands directly on your computer (which could be risky), the agent runs them inside a Docker container. The default OpenHands sandbox (python-nodejs:python3.12-nodejs22 from nikolaik/python-nodejs) comes with some packages installed such as python and Node.js but may need other software installed by default. You have two options for customization:
  • Use an existing image with the required software.
  • Create your own custom Docker image.
If you choose the first option, you can skip the Create Your Docker Image section.

Create Your Docker Image

To create a custom Docker image, it must be Debian based. For example, if you want OpenHands to have ruby installed, you could create a Dockerfile with the following content:
Or you could use a Ruby-specific base image:
Save this file in a folder. Then, build your Docker image (e.g., named custom-image) by navigating to the folder in the terminal and running::
This will produce a new image called custom-image, which will be available in Docker.

Using the Docker Command

When running OpenHands using the docker command, set -e SANDBOX_BASE_CONTAINER_IMAGE=<custom image name>:

Using the Development Workflow

Setup

First, ensure you can run OpenHands by following the instructions in Development.md.

Specify the Base Sandbox Image

In the config.toml file within the OpenHands directory, set the base_container_image to the image you want to use. This can be an image you’ve already pulled or one you’ve built:

Additional Configuration Options

The config.toml file supports several other options for customizing your sandbox:

Run

Run OpenHands by running make run in the top level directory.