Skip to main content

Quick Start with stn up

The simplest way to run Station in Docker:
This single command handles everything: building images, creating volumes, starting services, and configuring MCP endpoints.

Primary Use Case: Running Bundles

stn up is designed to make running agent bundles effortless. Whether from CloudShip, a URL, or a local file:
The bundle is automatically installed into the container’s default environment and all agents become available immediately.

Secondary Use Case: Testing Local Configurations

For developers building custom agents, stn up provides an isolated container environment that mirrors production:
This ensures your agents work correctly in the same containerized environment they’ll run in production, without affecting your local system.

Manual Docker Deployment

Using Docker Compose

Station provides a docker-compose.yml for production deployments:
Start with:

Building Custom Image

Build from source:
Or build with UI embedded:

Zero-Config Deployment

Station supports automatic bundle installation from mounted directories:
Drop .tar.gz bundle files in ./bundles/ and they install automatically on startup.

Environment Variables

Configure Station via environment variables:

Volume Mounts

Networking

Internal Docker Network

For container-to-container communication, use Docker’s internal DNS:

Host Network Access

From inside the container, access host services:
On Linux, add:

Health Checks

Add health checks for orchestration:

Kubernetes Deployment

Example Kubernetes deployment:

Troubleshooting

Container Won’t Start

Check logs:

Permission Issues

Station runs as user station (UID 1000). Ensure mounted volumes are accessible:

Port Conflicts

Check if ports are in use: