Verification checklist
- 1Download the release ZIP and the SHA256SUMS file.
- 2Run a local checksum verification before extracting anything.
- 3Confirm the calculated hash matches the published value exactly.
- 4Only proceed if the verification succeeds.
Why verify before first run
- +Artifact verification before execution
- +Private-by-default deployment posture
- +Minimal host-side lifecycle tooling to reduce drift
- +Explicit update and rollback procedures before incidents
If the hash does not match
- !Do not extract, load, or run the bundle.
- !Download the artifact and checksum file again before retrying.
- !If the mismatch persists, contact [email protected].
What happens after verification
- +Published SHA-256 checks let you verify exactly what enters your environment before first run.
- +Prebuilt image tarballs keep installs reproducible without maintaining your own image build pipeline.
- +A host-side operator wrapper standardizes validation, startup, logs, backup, update, rollback, and version checks.
- +Documented recovery procedures reduce downtime, operator guesswork, and one-person knowledge traps.
Need the full runtime boundary?
Review the runtime boundary, operational limits, and support scope before first run.