dstack

dstack

Overview

dstack provisions and orchestrates workloads across GPU clouds, Kubernetes, and on-prem via fleets.

When to use this skill:

• Running or managing dev environments, tasks, or services on dstack
• Creating, editing, or applying *.dstack.yml configurations
• Managing fleets, volumes, gateways, and checking available offers

How it works

dstack operates through three core components:

1. dstack server - Can run locally, remotely, or via dstack Sky (managed)
2. dstack CLI - Applies configurations and manages or inspects fleets, runs, logs, events, volumes, gateways, and offers; it uses project configurations stored in ~/.dstack/config.yml, which can be managed with dstack project
3. dstack configuration files - YAML files ending with .dstack.yml

dstack apply shows a plan and submits configuration changes. For run configurations, it attaches when the run reaches running by default: it configures SSH access, forwards declared ports, and streams logs. With -d, it submits and exits.

Quick agent flow (detached runs)

1. Show plan: echo "n" | dstack apply -f <config>
2. If plan is OK and user confirms, apply detached: dstack apply -f <config> -y -d
3. Check the run: dstack run get <run-name> --json
4. If dev-environment or task with ports and running: attach to surface IDE link/ports/SSH alias (agent runs attach in background); ask to open link
5. If attach fails in sandbox: request escalation; if not approved, ask the user to run dstack attach locally and share the output

CRITICAL: Never propose dstack CLI commands or YAML syntaxes that don't exist.

• Only use CLI commands and YAML syntax documented here or verified via --help
• If uncertain about a command or its syntax, check the links or use --help

NEVER do the following:

• Invent CLI flags not documented here or shown in --help