Configure a single custom sandbox image for the whole installation through the Replicated Admin Console.
This approach is deprecated. It configures one image for the entire
installation and does not support per-user image selection or multiple
simultaneous environments.New installations should use
Configuring Custom Sandbox Images
instead. This page is retained for installations that have not yet migrated.
Both approaches coexist — you can adopt warm runtime pools without removing
this setting.
Once your image is built and pushed to a registry, point the Replicated Admin
Console at it.
Open the Admin Console at https://admin.<your-base-domain>:30000.
Navigate to Config and find the Sandbox Configuration section.
Set the following fields:
Field
Value
Use a Custom Sandbox Image
Enabled
Sandbox Image Repository
Your image repository (e.g. ghcr.io/your-org/openhands-custom-image)
Sandbox Image Tag
Your image tag (e.g. v1.2.0)
Registry Server
If your registry requires authentication
Registry Username
If your registry requires authentication
Registry Password or Credentials
If your registry requires authentication
Click Save config and then Deploy to apply the change.
This single image becomes both the default for new conversations and the image
kept ready in the installer-managed warm pool.
This setting applies to the sandbox / agent-server image only — the
image that runs inside each agent’s isolated workspace. It does not replace
the other OpenHands service images.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.