Run Ride The Lightning independently as a container on Docker.
bitcoindrunning on a separate container- Use mu373/docker-bitcoind
- Container name:
bitcoind(we access RPC using this hostname) - Docker network:
bitcoin-nw
LNDrunning on a separate container- Use mu373/docker-lnd
- Container name:
lnd(we access RPC using this hostname) - RPC: HTTP(S) REST at port 8080
- Docker network:
bitcoin-nw
- traefik proxy running on a separate container
- Use mu373/traefik
- Docker network:
traefik-nw
Prepare configuration for rtl
cp docker-compose-template.yml docker-compose.yml
vim docker-compose.yml # Set lnd path and your custom hostname
cp Sample-RTL-Config.json RTL-Config.json
vim RTL-Config.json # Set the app password under `multiPass` field. Once you login using this password, it will automatically be converted to hashed password.Start the container
docker compose up -dAccess the shell inside the container
# In host
docker ps # Check container id
docker exec -it container_id bashSee logs
docker logs --tail 100 container_id- If you don't need reverse proxy and want to directly access RTL with HTTP:
- Comment out all the traefik related configs in
docker-compose.yml - Uncomment
portsconfig indocker-compose.yml - RTL should be available at
http://YOUR_IP_ADDRESS:3070
- Comment out all the traefik related configs in
- When the traefik is properly setup, you can access the RTL at
https://yourrtl.example.comat port 443. - Some practical hints
- Setup Tailscale in the host machine
- Create
AandAAAArecord atyourserver.example.com, pointing to the host Tailscale IP - Create
CNAMErecord atyourrtl.example.com, pointing toyourserver.example.com - Tweak traefik proxy configs in
docker-compose.yml - This way, you don't have to configure https and certificates within the RTL container yourself. Traefik works as a reverse proxy and does all the complicated stuffs for you.
- Options for
RTL-Config.jsonis listed here