Fix installing plugins in dockerfile #2451
Merged
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.
Current state
In docker, the lightning installation is achieved by copying binaries one by one ‘manually’. As soon as a new binary is added, the dockerfile become outdated. See #2377
What has been done
Binaries are installed into a temporary directory using
configure --prefix=
andmake install
, then the installation directory is copied ‘as-it-is’ to the final image in the second phase of the build. This will guarantee that any new lib/binary/plugin generated frommake install
will be reflected in the docker images, and more important, the docker image configuration is closer to the normal build.Note to the maintainers
Update the official docker image after the merge of this PR.