Plugins present in Docker distribution don't match binary distribution

[jblachly]

I have been trying fruitlessly to bring a lightningd container up alongside the rest of my infrastructure.

Finally, I realized that startup failures like grpc-host=0.0.0.0: unknown option are because the official blockstream docker image [1] (v25.05 , since there appears to be none newer than this) does not match the binary distribution [2].

binary distro	docker image
autoclean	autoclean
bcli	bcli
bookkeeper	bookkeeper
chanbackup	chanbackup
cln-askrene	cln-askrene
cln-grpc	cln-renepay
cln-lsps-client	cln-xpay
cln-lsps-service	commando
cln-renepay	exposesecret
clnrest	funder
cln-xpay	keysend
commando	offers
exposesecret	pay
funder	recklessrpc
keysend	recover
offers	spenderp
pay	sql
recklessrpc	topology
recover	txprepare
spenderp	wss-proxy
sql
topology
txprepare
wss-proxy

diff = 6,8d5
< cln-grpc
< cln-lsps-client
< cln-lsps-service
10d6
< clnrest

Why are these plugins missing from the image?

Certainly without external control (grpc and/or rest) my node is not very useful.

[1] https://hub.docker.com/r/blockstream/lightningd
[2] https://github.com/ElementsProject/lightning/releases/download/v25.05/clightning-v25.05-Ubuntu-24.04-amd64.tar.xz

[jblachly]

I see that there is also

https://hub.docker.com/r/elementsproject/lightningd

Could I convince you to nuke the blockstream/lightningd container repository?

[ShahanaFarooqui]

I see that there is also

https://hub.docker.com/r/elementsproject/lightningd

Could I convince you to nuke the blockstream/lightningd container repository?

Thanks for bringing this to our attention. I agree that maintaining them separately is confusing and unnecessary. I'll follow up internally to remove one of them. Keeping this issue open until we reach a conclusion.