Run Docker

The standard Adria image includes Docker Engine, Compose, and Buildx. Containers run inside your sandbox VM alongside your repository and coding agents.

Start your project's services

Connect from your local computer:

cube connect feature/payments

Sandbox: from a repository with a Compose file:

docker compose up -d
docker compose ps
docker compose logs -f

up -d runs the containers in the background. logs -f follows their output; Ctrl+C stops following logs and leaves the containers running.

Preview a containerized app

Publish the container's application port to the sandbox VM. For example, a Compose service listening on port 3000 in its container can publish it with:

ports:
  - "127.0.0.1:3000:3000"

The application inside the container must listen on an interface reachable through Docker's published port, usually 0.0.0.0.

Then run locally:

cube open 3000 --session feature/payments

The Adria tunnel connects to the VM's published port. Keep it running while using the preview. For databases and other TCP services, use cube forward.

Run several stacks in parallel

Start each branch in a separate sandbox to keep its containers, volumes, and service ports independent. Both sandboxes can publish the same remote port; use different local forwarding ports to reach them from your computer. See Parallel engineering.

Stop services and preserve data

Sandbox: stop the Compose project when finished:

docker compose down

Follow your Compose configuration's volume policy for data you need to keep. Pausing the sandbox preserves its disk but stops running processes. After resume, start services again as needed. Deleting the sandbox removes its disk, including Docker data stored there; export anything you need before deletion.