dougvk / lightning-node Goto Github PK

hi, i have setup a LN node, and i wanted to make sure its working properly.
apparently it does not.

docker logs 900xx7556xca
shows
error: exec failed: exec format error

to make sure its not running

docker ps -a
the status as exited right after starting the container.

CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS                     PORTS               NAMES
900xx7556xca        dougvk/bitcoind:latest   "/entrypoint.sh bitcâ¦"   5 minutes ago       Exited (1) 5 minutes ago                       bitcoind_mainnet

i have tried to delete everything and reinstalling everything from the beginning , deleted the container and rebuild it.
same story.

@dougvk

hardware are

4 Dedicated ARM Cores
2GB memory

guide i followed

https://steemit.com/bitcoin/@kimsekim/how-to-setup-bitcoin-lightning-maninnet-network-node

Needed to add --no-tty to gpg commands in Dockerfile for it to build in Centos 7

&& gpg --no-tty --import ./laanwj-releases.asc \
&& gpg --no-tty --verify SHA256SUMS.asc \

A pretty simple change that should work across the board. If you need more testing I can submit a pull request but figured it was small enough to just post here for others.

Hi guys,
Anyone has faced the same issue so far?
I've tried to delete appeared containers and run Bitcoind again it shows the same error.

sudo docker run --name bitcoind_mainnet -d -v /scratch/bitcoin/mainnet/bitcoind:/data -p 8333:8333 -p 9735:9735 dougvk/bitcoind:latest
docker: Error response from daemon: Conflict. The container name "/bitcoind_mainnet" is already in use by container "39b58f4dac954ae34cd694a5de26f6925702b31eca3cab56c62d935b95eea585". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

sudo docker logs bitcoind_mainnet --tail "10"
error from daemon in stream: Error grabbing logs: EOF

sudo docker ps -a
CONTAINER ID        IMAGE                    COMMAND                  CREATED             STATUS              PORTS               NAMES
39b58f4dac95        dougvk/bitcoind:latest   "/entrypoint.sh bitc…"   19 minutes ago      Created                                 bitcoind_mainnet

sudo docker start bitcoind_mainnet
fixed my problem.

how can I update to latest LN version ? can you guide me

It stuck at CHANNELD_AWAITING_LOCKIN.

lightning-cli listpeers

{ "peers" : 
        [ 
                { "id" : "0371190acfb2e92bd1faa6ce4d12ff248798515a92ac903ac14d31b5172d9b2917", "connected" : true, "netaddr" : 
                        [ "176.9.113.240:9735" ], "channels" : 
                        [ 
                                { "state" : "CHANNELD_AWAITING_LOCKIN", "owner" : "lightning_channeld", "short_channel_id" : "511369:160:1", "funding_txid" : "a42ee5a910d20e71f7707e0fff1756d9f31562032ebd3fddf0a75f0c9f2
cd7f8", "msatoshi_to_us" : 200000000, "msatoshi_total" : 200000000, "dust_limit_satoshis" : 546, "max_htlc_value_in_flight_msat" : 18446744073709551615, "channel_reserve_satoshis" : 0, "htlc_minimum_msat" : 0, "to_self
_delay" : 144, "max_accepted_htlcs" : 483 } ] } ] }

How do I set the name of my new node?

Hello, I am following your article on medium and trying to get things setup on a vps with the docker image. When downloading the blockchain with bitcoind_mainnet, the download just stops without error message.

The last item I see in the logs this time after running it again is:
2018-01-29 15:17:56 UpdateTip: new best=00000000000001a8f5d064729e3ea4370fa93dc174e77d6653f955729aae85bb height=173770 version=0x00000001 log2_work=67.926403 tx=2730207 date='2012-03-31 19:25:24' progress=0.009362 cache=221.9MiB(1651915txo)

I'm using a cheapish vps with only 512mb of ram, is this possibly the culprit? Or have any other ideas? It does seem to stop at different blocks each time I restart so not sure if it's the memory or not.

I tried to update the base image to ubuntu:latest or debian:bullseye-slim in your Dockerfile and with either base image I get to step 5 and it reports that /usr/bin/gpg-agent cannot be found. The signature checks work when the base image is stretch-slim. Any idea what I'm missing?

Thanks for the work and the great Medium post.

Hi!

I followed your tutorial, but instead of DigitalOcean, i did it all on a Linux VM on my computer, and now i have the bitcoin and lightning docker running. I also have an opened channel with funds i've just added.
If i kill the docker instance or restart the VM, will i lose access to this channel + funds ? Or is it possible to reconnect to the channel later ? I'm afraid of restarting my computer and losing access to my funds.

Thanks !