Platform Deployment · PD-07

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.

RUNTIME & STATE

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.

For disk or mount changes after installation, follow Configure Persistent Storage → to migrate data safely. 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

Interface tour

REFERENCE 01

STRATUM Container Runtime

Confirm that the STRATUM container is running in the selected Docker or Podman runtime and note the active container/image state.

Commands

Use either Docker or Podman, whichever STRATUM Host Manager is configured to run. Container names may differ for additional worker instances.

shell

# Docker example: inspect the active image and container
sudo docker images
sudo docker ps -a
sudo docker inspect stratum | head -n 15

# Podman deployments: use the equivalent commands
# sudo podman images
# sudo podman ps -a
# sudo podman inspect stratum | head -n 15

REFERENCE 02

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.

Commands

The directory can contain enrollment tokens, private keys, and certificates. Do not paste file contents into tickets or public logs.

shell

# Show configuration file paths without exposing key material
sudo find /etc/stratum -maxdepth 3 -type f -print | sort
sudo ls -ld /etc/stratum /etc/stratum/secure /etc/stratum/certs

REFERENCE 03

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.

Commands

The default persistent root is /persistent/stratum. If you changed it in Host Manager, substitute the configured path.

shell

# Inspect the configured persistent root and available capacity
sudo find /persistent/stratum -maxdepth 4 -print | head -n 25
sudo du -sh /persistent/stratum
df -h /persistent/stratum

REFERENCE 04

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.

Commands

Run from the directory containing stratum-host, or omit ./ if it is installed on your PATH.

shell

# Discover the supported CLI actions and quick starts
./stratum-host --help | head -n 30

# Show proposed host changes without applying them
./stratum-host plan

REFERENCE 05

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.

Commands

Read the earliest relevant error rather than restarting repeatedly. Logs can include sensitive hostnames and operational details; sanitize before sharing.

shell

# Read recent startup and runtime logs
sudo docker logs --tail 100 stratum

# To follow live startup errors
sudo docker logs --follow --tail 50 stratum

# Podman: replace docker with podman

RESULT

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.