What happened.

Hydra updated its demo docker-compose cardano-node image after moving its devnet configuration off legacy tracing. The record identifies a clear startup failure on cardano-node 10.6.2: “Missing LogMetrics.” It says 11.1.2 was tested directly against the configuration and started successfully.

Why it matters.

For operators making the same tracing-config migration, the result provides a specific failure signature and tested image outcomes. It suggests that a tracing migration and node-image update may need to be handled together, rather than treating the error as proof that the configuration itself is malformed.

What to watch.

Watch for a follow-up compatibility test or release note that defines the supported node-version range for configurations migrated off legacy tracing. That would clarify where compatibility begins, which this record does not establish.

What to watch

A documented compatibility range or further direct tests across node versions.

Sources and limits

Upstream references and independent checks

Digest dated 2026-09-23 · upstream model sonnet. Direct links are matched to all 1 upstream source IDs.

  1. 1
    Bump demo docker-compose cardano-node image to 11.1.2Direct upstream source · 1a662c3443928742f34995f53d02b4a2287212a2

This Research brief was generated by Terra from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: This is a single official-repository record from Hydra’s demo/devnet setup; it does not establish mainnet impact or the exact version at which the configuration became incompatible.