When to use Daytona
Use Daytona when:- task work should run outside the Roomote host
- you want hosted sandboxes with simple credential setup
- you can provide a Daytona API key
- environment setup caching or task sleep/resume via snapshots is useful
Configuration
Add Daytona from Settings > Sandboxes with your API key, or provide the values as deployment env vars. Create the key on the API Keys page with write and delete permissions on both Sandboxes and Snapshots. No other scopes are needed.DAYTONA_API_URL for custom Daytona endpoints. Use DAYTONA_TARGET when
your account or deployment needs a specific target or region.
Roomote’s Daytona worker snapshot includes Docker and Docker Compose, so
environments can run
Docker projects. Daytona
runs these through Docker-in-Docker inside the task sandbox. Container builds
and services share the sandbox’s resources. Roomote requests 8 GiB for these
tasks and 4 GiB for tasks that do not need nested Docker.
Verify setup
- save
DAYTONA_API_KEY - select Daytona as the default sandbox provider
- start a small task from an environment
- confirm the task starts, streams logs, and can run project commands
- verify preview links if the task starts a web app
Common issues
- The provider starts in the wrong region or target. Set
DAYTONA_TARGETto the intended target. - Container startup is slow or runs out of memory. Increase the Daytona sandbox resources; Docker-in-Docker adds daemon and image-build overhead.