Skip to main content
Start with lstack status, then use lstack doctor for a broader diagnostic pass.

​
Check status

Status distinguishes a stopped core from a running but unhealthy core. It reports the effective port, running version, uptime, and Docker availability.

​
Run doctor

Doctor checks configuration, private-path permissions, database integrity, process state, port state, version identity, update state, and Docker availability.
Docker being unavailable is reported as a warning. The dashboard core can remain healthy without Docker.

​
Inspect logs

The command returns the most recent 200 core log lines. Use --worker <name> or --runtime <name> to inspect a managed container instead.

​
Create a support bundle

The support bundle contains allowlisted diagnostic material and passes output through the product’s redaction controls. Review the bundle before sharing it.

​
Recovery sequence

  1. Run lstack status.
  2. Run lstack doctor.
  3. Inspect recent logs.
  4. Confirm Docker separately when the problem affects workers or runtimes.
  5. Create a support bundle if the issue remains unresolved.