archetech / archon / 28707821531

92%

main: 92%

Pull #692

github

fix(compose): CLN rune-init containers must use the same image as the node

The lightning compose ran the CLN node on ghcr.io/lightning-goats/cl-hive-node
(default 3.4.0) but the three one-shot rune-init containers (drawbridge-init,
rtl-init, lnbits-init) on ghcr.io/archetech/cl-hive-node (default 2.13.2) — a
different fork on a different versioning scheme, yet both keyed off the same
${ARCHON_CLN_VERSION}. So the init `lightning-cli` came from a different
image/version than the running lightningd, and setting ARCHON_CLN_VERSION to a
node tag (e.g. 3.4.0) would make the init containers pull a nonexistent
archetech tag. The archetech/cl-hive-node:2.13.2 tag is also not publicly
resolvable, whereas the node's lightning-goats:3.4.0 image is public and
verified to ship bash + python3 + lightning-cli (all the init scripts need).

Introduce a shared `x-cln-image` YAML anchor pointing at the node's image and
reference it from the node and all three init containers, so the init CLI always
matches the running lightningd and a version bump moves them together. No change
to the rtl/lnbits images. `docker compose config` confirms all four CLN services
resolve to ghcr.io/lightning-goats/cl-hive-node:3.4.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2816 of 3323 branches covered (84.74%)

Branch coverage included in aggregate %.

5851 of 6142 relevant lines covered (95.26%)

882.15 hits per line