Runtime, Persistent State & Logs
Know where the replaceable application image ends and persistent STRATUM state begins. These paths and logs are the first place to look when host startup is not behaving as expected.
Know what is replaceable and what persists
The STRATUM container is the replaceable application runtime. Host configuration, credentials, logs, and durable controller data live outside that image on the host. A STRATUM upgrade is therefore a new container image tag: start the new tag against the existing host state. If a rollback is required, select the earlier image tag and start that version again.
When troubleshooting, first confirm which container is running, then inspect /etc/stratum, the persistent STRATUM data paths, and the container logs. That separates an application-image problem from a host-configuration or persistent-state problem.
Interface tour
STRATUM Container Runtime
Confirm that the STRATUM container is running in the selected Docker or Podman runtime and note the active container/image state.
STRATUM Etc Configuration Layout
Use /etc/stratum for host and controller configuration, generated configuration files, certificates, keys, and other host-managed settings. On the controller, the generated HTTPS certificates can be replaced with the organization’s own certificate and key. Workers do not host the controller HTTPS certificate set, so there are no equivalent web certificates to manage on worker nodes.
STRATUM Persistent Data Layout
Durable STRATUM runtime data is stored outside the replaceable container image, including logs, the controller database, authentication data, and VM disk images. This is the state that survives an application-image replacement.
STRATUM Host CLI Help
Run stratum-host --help when you need the supported controller, compute-worker, or storage-worker quick-start commands and command-line options.
STRATUM Container Logs
Inspect the STRATUM container logs when the container starts but the application does not reach a healthy state. Read the first reported failure, correct the underlying configuration, dependency, permission, or resource problem, and then restart. Repeating the same start without changing the failing condition will normally reproduce the same error.
The outcome you should see
You can identify the running STRATUM container, the host configuration under /etc/stratum, the durable data paths, and the logs used to diagnose startup or runtime problems.