Skip to content

executor-v1.181

Choose a tag to compare

@millerserhii millerserhii released this 12 Nov 12:07
a7ddbec

What's Changed

  • DAH-5785 - [P1] Validator: bound the stale container cleanup step by @surcyf123 in #2075
  • DAH-6148 - [P1] Validator: Lium's backup helper is not the provider's CPU load by @lium-loop[bot] in #2182
  • DAH-6066 - [P0] Rental memory limit sized from the host's idle free memory by @surcyf123 in #2163
  • DAH-5832 - [P0] CI: run tests and e2e-gate once a PR is approved by @lium-loop[bot] in #2101
  • DAH-5729 - [P0] Rental SSH: refuse a hostname node whose host key is not its registered one by @lium-loop[bot] in #2203
  • DAH-5762 - [P1] Validator: the rented pod ownership check also reads the sudo files by @surcyf123 in #2208
  • DAH-5869 - [P1] Validator: report a visible but failing GPU on a rented node by @lium-loop[bot] in #2112
  • DAH-6186 - [P1] Validator: a pod that holds a node's whole port range drops a held extra port instead of failing by @surcyf123 in #2194
  • DAH-6222 - [P1] Validator: a filler the validator removed itself is not a host kill by @surcyf123 in #2206
  • DAH-6029 - [P1] Validator: wait out the image's apt lock before the main-only SSH install by @lium-loop[bot] in #2211
  • DAH-6248 - [P2] Runner waits for an open validator SSH session before recreating the executor by @surcyf123 in #2212

Full Changelog: executor-v1.180...executor-v1.181

CVM attestation

  • Approved executor-runner digest (EXECUTOR_RUNNER_IMAGE_DIGEST in .env): sha256:f8421a1d93c62029326e86bbd5ad5192c480477c68e87811fe4084bd499c854c (the runner image pushed 2026-10-26; the approved digest does not change per release, so this digest is older than the release and still the approved one)
  • Expected compose hash of a CVM created from this release: 0cc30085543511090db2952809f104dd30ec7d8630abb9fc4cde8590068ec104

Check after sudo ./lium-cvm.sh new <name> and before run:

sha256sum run/vms/<name>/shared/app-compose.json

From the checkout, python3 scripts/compose_hash.py --check run/vms/<name>/shared/app-compose.json does the comparison and exits 1 on a mismatch.

The output must equal the expected compose hash. Any other value means the measured files or the digest differ from the release, and the validator does not know the hash. What that costs depends on the validator's whitelist enforcement (ENABLE_ATTESTATION_WHITELIST): with it on, the validator rejects the CVM and it scores zero; with it off (the default), the validator accepts the unknown hash and scores the node as before. Do not run a CVM that does not match the release either way. Under enforcement a matching value scores only once the validator release that whitelists this hash is deployed; until then a correct CVM scores zero as well.