Repository navigation
executor-v1.183
What's Changed
- DAH-6066 - [P0] Revert rental memory limit sized from the host's idle free memory by @surcyf123 in #2242
- DAH-6269 - [P2] Validator: pass DinD pod storage sizes to Docker as whole numbers by @lium-loop[bot] in #2217
- DAH-6169 - [P2] Validator get()/post() sign the whole request; drop the timestamp-only signer by @lium-loop[bot] in #2221
- DAH-5802 - [P1] Validator: a GPU the create step cannot attach hides the node from new rentals by @surcyf123 in #2091
- DAH-6251 - [P1] Validator: executor stack excused by id plus one container by @lium-loop[bot] in #2225
- DAH-6277 - [P1] Validator: a rent's disk clamp never raises its order, and ghost containers no longer stop the volume sweep by @surcyf123 in #2219
- DAH-6354 - [P3] Remove dead validator settings and past date switches by @surcyf123 in #2235
- DAH-6381 - [P1] Validator: an ownership shift after a container-only restart does not blame a host shutdown by @lium-loop[bot] in #2244
- DAH-6451 - [P1] Pinned-memory probe: time limit for the copy only, so slow CUDA setup stops failing 8-GPU TDX nodes by @lium-loop[bot] in #2263
- DAH-6295 - [P0] Validator: a node on another GPU model is reset once, then verified as it is now by @surcyf123 in #2222
- DAH-6328 - [P1] Spot idle pay is 0.9x what Default Jobs earn, Secure unchanged by @surcyf123 in #2231
- DAH-6410 - [P3] A create step that fails after the renter's delete is reported as the renter's cancel by @surcyf123 in #2251
- DAH-4909 - [P4] Remove ENABLE_GPU_ATTESTATION: CVM executors always emit GPU evidence by @lium-loop[bot] in #1774
- DAH-6133 - [P1] Validator: the port check starts its host listener alongside the outside reading by @lium-loop[bot] in #2176
- DAH-6326 - [P1] validator: a power cap at the default limit no longer hides a GPU held under half its clock by @surcyf123 in #2229
Full Changelog: executor-v1.182...executor-v1.183
CVM attestation
- Approved executor-runner digest (
EXECUTOR_RUNNER_IMAGE_DIGESTin.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.jsonFrom 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.