Closed robertclarkson closed 3 years ago
Further to this, the most recent version i can get to load is 0.4.13
If i use 0.4.16 i get
lightning-charged_1 | Connecting to bitcoind at 192.168.10.2:8332... waiting for RPC... ready.
lightning-charged_1 | Starting lightningd... waiting for RPC unix socket... Refusing to migrate down from version 129 to 128
I was able to get your docker-compose to work the latest version (v0.4.22). I didn't try with v0.4.19, is there a particular reason you're using it?
You can try running docker exec -it <id> tail -f /data/lightning/regtest/debug.log
to see c-lightning logs, which might provide a hint.
I would, however, recommend to use a separate container for c-lightning and use the shesek/lightning-charge:standalone
docker image (comes with lightning charge only, without bitcoind/lightningd). The c-lightning version that comes bundled with charge is behind by 4 versions, which is quite significant in the lightning world.
I will look into updating the bundled c-lightning, but you're probably still better off using it directly so you'll get updates sooner.
If you're looking for more of an all in-one-one solution, I have another project coming up that might be relevant. It won't include lightning charge initially, but its high on the priority list. Will send a ping here when its released.
The bundled c-lightning was updated to the latest release (v0.9.3).
Closing this for now, please report back if you're still having issues.
Hi my docker compose service looks like this:
I get the log message
But then doesnt load clightning.
if i use container version 0.3.15 then it works but i'm on a super old version of lightning.
Can anyone help? Thanks