This vs official containers
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 7
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure if you are aware of them, but lnd has [official containers](https://github.com/lightningnetwork/lnd/blob/master/docs/DOCKER.md) which [can be verified](https://github.com/lightningnetwork/lnd/blob/master/docs/DOCKER.md#verifying-docker-images). Does it make sense to still keep this repo around and maintained when there is an official solution?
(Your dockerized apps are amazing, but when there are official containers, I don't understand why you should use this and not the official ones)
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
The issue points to lnd's official Docker documentation, including its image-verification section; read those materials first and compare them with this repository's stated multi-architecture purpose. No file, test, or concrete change is named, so completion would require a maintainer decision about whether continued maintenance is justified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100