lightninglabs / lightninglabs/lndinit
build docker images with lndinit built from the same lnd version as the lnd version it is paired with inside the container image
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 37
- Forks
- 18
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 1
Description
When running
I get
2026-07-17 00:20:34.435 [INF]: LNDINIT Version 0.1.36-beta commit=docker/v0.1.36-beta-lnd-v0.21.0-beta, debuglevel=error
...
2026-07-17 00:20:35.091 [INF] LTND: Version Info rev=2b8788 version=0.21.1-beta commit=v0.21.1-beta debuglevel=production logging=info
which is confusing because first lndinit reports lnd-v0.21.0-beta and then lnd reports 0.21.1-beta.
lndinit and lnd should be bundled in the same docker image using the same lnd version.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Docker image build that produced the referenced lndinit image and follow how the lndinit and lnd version tags are selected. Verify the build inputs against the reported image logs; done means both bundled components report the same lnd version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100