Synaro

Synaro docs

Environments & Docker

How Synaro provisions containers, exposes previews, and manages runtime state.

The environment-service talks to the local Docker socket (or cluster runtime in production) to create isolated workspaces per project. Status flows back to the UI as INACTIVE, PROVISIONING, RUNNING, STOPPED, or ERROR.

Lifecycle

  1. User starts Docker from the workspace toolbar
  2. Service clones or mounts the project workspace and selects a base image
  3. Container runs with CPU/memory limits and network policy
  4. Terminal WebSocket attaches for interactive shells
  5. Stop or destroy releases resources

Preview & run

When RUNNING, the Run control executes your start command and streams logs into the workspace log panel. The preview iframe loads the published preview URL (often localhost ports forwarded from the container).

Many third-party sites block iframe embedding (X-Frame-Options). Use URLs you control for reliable previews.