Start and Stop Docker Teranode
Last modified: 28-April-2026
Use the scripts in
teranode-quickstart
instead of invoking Docker Compose directly. The scripts load .env, use the
right Compose profiles, handle FSM transitions, and keep common commands
consistent.
Start
From the quickstart repository root:
./start.shstart.sh runs docker compose up -d, then performs the Teranode FSM startup
transition. It always prints the local URLs for the asset viewer and RPC. When
the monitoring profile is enabled, it also prints Grafana, Prometheus, and
Kafka Console URLs.
Check service state:
./status.shThe status script shows:
- Docker Compose service status
- Teranode FSM state
- Chain information through RPC
Logs
Tail all logs:
./logs.shTail a specific service:
./logs.sh blockchain
./logs.sh asset
./logs.sh p2pUse the service names from docker compose ps when you need a different
container.
RPC and CLI Checks
Quickstart wraps common calls so credentials and container names do not need to be repeated:
./rpc.sh getblockchaininfo
./rpc.sh getblockcount
./cli.sh getfsmstateIf the FSM startup transition races during boot, set it manually:
./cli.sh setfsmstate --fsmstate RUNNINGStop
Use the stop script for normal shutdown:
./stop.shstop.sh asks Teranode to enter IDLE state, then runs docker compose down.
Data volumes are preserved.
Restart
For a normal restart:
./stop.sh
./start.sh
./status.shDirect Docker Compose Use
Direct docker compose commands are still useful for advanced inspection:
docker compose ps
docker compose logs -f blockchain
docker compose configRun them from the quickstart repository root so Compose reads the correct
docker-compose.yml and .env.