Run kombify Simulate on your own server using Docker Compose. Simulate is a local-first development tool with no authentication required by default.Documentation Index
Fetch the complete documentation index at: https://docs.kombify.io/llms.txt
Use this file to discover all available pages before exploring further.
Requirements: Docker 24+ and Docker Compose v2 on Linux, macOS, or Windows with WSL2.
Quick start
Port mapping
| Port | Purpose |
|---|---|
5270 | REST API and web interface |
30000-39999 | SSH access to simulated nodes |
Environment variables
| Variable | Default | Description |
|---|---|---|
KOMBISIM_PORT | 5270 | API server port |
KOMBISIM_DATA_DIR | /data | Data directory (SQLite storage) |
KOMBISIM_LOG_LEVEL | info | Log verbosity: debug, info, warn, error |
KOMBISIM_ENGINE | docker | Simulation engine (see below) |
Engine selection
Simulate supports multiple engines for running simulated nodes. Set the engine via theKOMBISIM_ENGINE environment variable.
- Docker (default)
- Incus
- QEMU
- Azure
- DigitalOcean
Uses Docker containers to simulate nodes. Requires the Docker socket to be mounted.Best for: local development, CI/CD pipelines, lightweight simulations.
The Docker engine is the default and requires no additional setup beyond mounting the Docker socket. Cloud engines (Azure, DigitalOcean) require provider credentials configured in Simulate.
Verify installation
Data persistence
Simulate stores all state in SQLite within the/data directory. The ./data bind mount ensures data survives container restarts and upgrades.
To back up your Simulate data:
Troubleshooting
Container fails to start
Container fails to start
- Port conflict: Another process is using port 5270 or ports in the 30000-39999 range.
- Docker socket not available: Ensure
/var/run/docker.sockexists and is accessible.
Cannot SSH into simulated nodes
Cannot SSH into simulated nodes
- Confirm the node is running: check the API or web interface
- Verify ports 30000-39999 are not blocked by a firewall
- Use the port shown in the node details, e.g.
ssh -p 30001 root@localhost
Engine not working
Engine not working
- Docker engine: Verify the Docker socket is mounted and the Docker daemon is running
- Incus/QEMU: These engines require the respective tools installed on the host
- Cloud engines: Check that provider credentials are configured correctly
Next steps
Templates
Use pre-built templates for common simulation setups
SSH access
Connect to your simulated nodes via SSH
