feat(images): add support for Core Lightning v23.08 #774
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #772
Adds support for Core Lightning v23.08.
This PR is not yet fully functional due to the latest release breaking compatibility with the c-lightning-REST plugin which Polar uses. In Core Lightning v23.08, a new
clnrest
plugin was added and enabled by default. When both of these plugins are enabled,lightningd
will fail to start with the error:There is a short-term workaround which is to disable the included
clnrest
plugin using the flag--disable-plugin=clnrest.py
, then thec-lightning-REST
plugin will function as it has previously. This will require a new release of Polar in order to make sure this flag is only passed to CLN nodes v23.08 and higher. The downside is that devs using Polar won't be able to use the new REST support.The long-term solution would be to update Polar to use the new
clnrest
plugin for it's communication with thelightningd
API. I want Polar to continue to support older CLN nodes, so it would still have to be able to use thec-lightning-REST
API untilv23.05.2
and below are completely phased out. I try to support the last 3-4 more major versions of node implementations, so this could take a year or more. Until that happens, Polar will need to support both REST APIs side-by-side.I am opening this PR now since some of the work is done. The docker images are pushed to Docker Hub and I am able to get the new CLN release to run in Polar as long as I manually add the
--disable-plugin=clnrest.py
flag via Advanced Options. It's going to take a bit more work to decide on a path forward then implement the changes necessary.