docker lnd not working

[awb99]

Background

I want to run lightening via docker images for mainnet:
Bitcoind is working:

export NETWORK="mainnet"
docker-compose up -d "btcd"

Lightening is NOT working:

export NETWORK="mainnet"
docker-compose run -d --name bob lnd_btc
docker exec -i -t bob bash

Your environment

• version of lnd
  latest gihub commit
• which operating system (uname -a on *Nix)
  manjaro / arch
• version of btcd, bitcoind, or other backend
  latest gihub commit

Steps to reproduce

bash-4.4# cat lnd.log
2019-03-23 18:36:19.138 [WRN] LTND: open /root/.lnd/lnd.conf: no such file or directory
2019-03-23 18:36:19.139 [INF] LTND: Version: 0.5.2-99-beta commit=queue/v1.0.1-136-g6ad8be25e1aaf4700bd86303ae534cf36c6199bf, build=production, logging=default
2019-03-23 18:36:19.139 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-03-23 18:36:19.198 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8
2019-03-23 18:36:19.198 [INF] RPCS: Generating TLS certificates...
2019-03-23 18:36:19.205 [INF] RPCS: Done generating TLS certificates
2019-03-23 18:36:19.339 [INF] LTND: Primary chain is set to: bitcoin
2019-03-23 18:36:19.369 [INF] LTND: Initializing btcd backed fee estimator

I think something goes wrong with "Initializing btcd backed fee estimator"
Also it seems LTND daemon is not running:

bash-4.4# netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 127.0.0.11:40215        0.0.0.0:*               LISTEN      
udp        0      0 127.0.0.11:41394        0.0.0.0:*                           
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node Path
bash-4.4# 

[wpaulino]

What does lnd's stdout/stderr show? It's possible that the node is exiting because it can't connect to btcd.

[awb99]

@wpaulino I think it is the docker-compose setting that was somehow bad. I think there are several
"reasons". First, I think it is firing off multiple LND instances with docker-compose up. When I limited
it to one LND, then LND would move below the backend fee estimation issue. The other issue is that
RPC certificates are getting wrong over time, due to docker-compose issuing different ip adresses
over time. So I added some hacks to the start-lnd.sh script:

# Remove TLS certificates (docker-compose does not re-assign the same IP address; therefore certificates might be wrong)
rm /root/.lnd/tls.cert
rm /root/.lnd/tls.key

[awb99]

I found out the issue in the BTCD dockerfile. I think it is a bug of docker-compose or docker, and happens RANDOMLY, and not only on all machines.

The certificates that are generated do not include the hostname inside the docker-compose network.
Therefore the certificates are bad, and LND cannot connect.

  && "/bin/gencerts" --host="*" --host="btcd" --directory="/rpc" --force

By adding --host="btcd" it works. Possibly in your dockerfile this needs to be called rpcserver.

[yancyribbens]

@awb99 I created a PR to enable docker-compose up here. feedback welcome.