dstack-prototyping

Prototype and verify dstack model-serving configurations on real GPU hardware before service deployment.

2.2k|256|Updated Jan 4, 2022
One-click install
npx skills add https://github.com/dstackai/dstack --skill dstack-prototyping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dstack-prototyping
Source: https://github.com/dstackai/dstack/tree/main/skills/dstack-prototyping
Command: npx skills add https://github.com/dstackai/dstack --skill dstack-prototyping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying a model-serving configuration on dstack without prior validation often fails due to untested images, commands, resources, or backend choices. This Skill guides a task-first prototyping workflow so the serving setup is proven on real hardware before being submitted as a dstack service.

Core Features & Use Cases

  • Task-First Prototyping: Start a long-lived dstack task, attach or SSH into it, and test the serving image, model download, cache path, command, port, launch flags, and a real model request before submitting a service.
  • Backend and Fleet Selection: Choose VM-based backends, SSH fleets, or Kubernetes fleets that reuse idle instances and instance volumes for caching model weights across runs.
  • Serving Source Verification: Consult vLLM recipes, SGLang docs, and release notes to pick the correct image, flags, and expected model behavior.
  • Use Case: When serving a new reasoning model with vLLM on dstack, prototype the full serving command inside a task, verify reasoning output via a local request, then submit the identical configuration as a service and confirm it through the dstack service URL.

Quick Start

Use the dstack-prototyping skill to test my vLLM serving configuration for this model in a dstack task before submitting it as a service.

Frequently Asked Questions about dstack-prototyping

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a dstack service configuration before deploying it?

Submit a long-lived dstack task with an idle command like sleep infinity, attach or SSH into it, and test the image, model download, serving command, port, and a real model request. Only submit the service after the task verifies the full configuration.

How do I choose a dstack backend or fleet for model serving?

Pick the offer whose hardware best fits the goal, then prefer VM-based backends, SSH fleets, or Kubernetes fleets when comparable. These reuse idle instances and instance volumes, so model weight caches persist across runs, unlike container-based backends.

Should I use vLLM or SGLang for serving a model on dstack?

Check the serving-framework sources before deciding: vLLM recipes at recipes.vllm.ai and SGLang docs at docs.sglang.io list supported models, launch flags, and expected behavior. Release notes on GitHub confirm version-specific model support.

Why does my dstack service fail even though GPU checks passed?

GPU visibility, imports, logs, or health endpoints alone do not prove a working setup. You must start the server inside a task and send a request that uses the requested model, verifying behavior such as reasoning output before submitting the service.

How do I run a long-lived serving process inside a dstack task over SSH?

Launch it with nohup, redirect stdin from /dev/null, and redirect stdout and stderr to a log file so the SSH command returns while the process keeps running, for example nohup vllm serve ... </dev/null > /tmp/vllm.log 2>&1 &.