dev.Dockerfile: allow forcing an lnd version

We can now use the `LND_VERSION` build argument to force a specific LND
version to be used when building. If the `LND_VERSION` build argument is
not set, then build continues as before this change and uses the version
already defined in `go.mod` and `go.sum`.
This commit is contained in:
ZZiigguurraatt 2025-06-16 11:57:22 -04:00
parent 2bc7e7f044
commit 2d3379b422

View file

@ -30,9 +30,11 @@ COPY --from=nodejsbuilder /go/src/github.com/lightninglabs/lightning-terminal /g
# queries required to connect to linked containers succeed.
ENV GODEBUG netdns=cgo
# Allow forcing a specific taproot-assets version through a build argument.
# Allow forcing a specific lnd and taproot-assets version through a build
# argument.
# Please see https://go.dev/ref/mod#version-queries for the types of
# queries that can be used to define a version.
ARG LND_VERSION
ARG TAPROOT_ASSETS_VERSION
# Need to restate this since running in a new container from above.
@ -41,6 +43,11 @@ ARG NO_UI
# Install dependencies and install/build lightning-terminal.
RUN apk add --no-cache --update alpine-sdk make \
&& cd /go/src/github.com/lightninglabs/lightning-terminal \
# If a custom lnd version is supplied, force it now.
&& if [ -n "$LND_VERSION" ]; then \
go get -v github.com/lightningnetwork/lnd@$LND_VERSION \
&& go mod tidy; \
fi \
# If a custom taproot-assets version is supplied, force it now.
&& if [ -n "$TAPROOT_ASSETS_VERSION" ]; then \
go get -v github.com/lightninglabs/taproot-assets@$TAPROOT_ASSETS_VERSION \