Create Dockerfile. Release Docker image and add to popular nodes app-stores.

[Reckless-Satoshi]

Is your feature request related to a problem? Please describe. Lnproxy works, it's a good idea and it is loved. Proof of this is its integration into Raspiblitz. Now it is time it is made easy to "run-and-forget" for anyone else. In addition, there is a chance the current service has compatibility issues with some base systems (e.g. dev lnproxy is down for this reason). This is a final solution to it as well.

Describe the solution you'd like Create a Dockerfile for a Lnproxy service that 'will just work'.

Additional context

• Here an example and steps to dockerize a service and add it to the Umbrel app store (https://github.com/getumbrel/umbrel-apps#a-good-dockerfile).
• Once ready it is extremely easy to port to other node implementations e.g. Citadel, Start9, etc.
• No more incompatibilities with the base system.

Other considerations

• Sticking to semantic versioning for the releases and the docker builds is a good idea.
• Ideas for the app pitch on the store cover images (a few will be needed) 1) "Earn Sats by relaying payments" 2) "Be a Lightning VPN! Provide privacy" 3) "Get paid by helping light mobile nodes find routes" (... just ideas ^^)
• Extra: might be a bit of an overhead, but it is convenient to create a GH workflow to automatically build and publish docker images everytime a new tag is created. Once a new tag is pushed, a new docker image is published and a couple days later every user has the up-to-date Lnproxy, very seamless! To see an example of how this work one can check https://github.com/Reckless-Satoshi/robosats/blob/main/.github/workflows/release.yml (creates robosats-client docker images, the lnproxy one can be much simpler!)

[lnproxy]

Yes! This will be the solution to my kernel bug woes.

[nir3shprabu]

https://github.com/lnproxy/lnproxy/pull/18 ✅

• [x] multi-stage builds for smaller size images. The final image weighs less than 10megs
• [x] Doesn't run service as root
• [x] Development files are not included in the final image
• [x] Chainguard distroless images as base images: The distroless container images contain only the application and its runtime dependencies. There is no shell or package manager and thus have a de facto smaller attack surface

The final image build was run through trivy to test for vulns and the result:

Before version bump of golang.org/x/net

After version bump of golang.org/x/net

[lnproxy]

Merged.

@Reckless-Satoshi if you get a chance, would be awesome to have someone that actually knows how to use docker test the the Docker file.