search

cdecker / kugelblitz

Controlling lightning
MIT License
19 stars 7 forks source link

bitcoin fails to start in docker container #1

Open bockha opened 7 years ago

bockha commented 7 years ago

I just tried to start up the docker container but it seems to fail starting bitcoin.

$ docker run -p 19735:19735 -v `pwd`/bitcoin:/bitcoin -v `pwd`/lightning:/lightning cdecker/kugelblitz:latest
2017-08-23 06:29:45,786 CRIT Supervisor running as root (no user in config file)
2017-08-23 06:29:45,786 WARN Included extra file "/etc/supervisor/conf.d/supervisor.conf" during parsing
2017-08-23 06:29:45,799 INFO RPC interface 'supervisor' initialized
2017-08-23 06:29:45,799 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2017-08-23 06:29:45,799 INFO supervisord started with pid 1
2017-08-23 06:29:46,804 INFO spawned: 'kugelblitz' with pid 7
2017-08-23 06:29:46,808 INFO spawned: 'bitcoin' with pid 8
2017-08-23 06:29:46,816 INFO spawned: 'lightning' with pid 9
2017-08-23 06:29:46,849 INFO exited: bitcoin (exit status 1; not expected)
2017-08-23 06:29:47,850 INFO success: kugelblitz entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-08-23 06:29:47,854 INFO spawned: 'bitcoin' with pid 15
2017-08-23 06:29:47,856 INFO success: lightning entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-08-23 06:29:47,891 INFO exited: bitcoin (exit status 1; not expected)
2017-08-23 06:29:49,895 INFO spawned: 'bitcoin' with pid 16
2017-08-23 06:29:49,930 INFO exited: bitcoin (exit status 1; not expected)
2017-08-23 06:29:52,938 INFO spawned: 'bitcoin' with pid 17
2017-08-23 06:29:52,972 INFO exited: bitcoin (exit status 1; not expected)
2017-08-23 06:29:53,974 INFO gave up: bitcoin entered FATAL state, too many start retries too quickly
cdecker commented 7 years ago

Looks like your bitcoin and lightning directories are not writeable by the user running the daemons, try the following:

sudo chown -R 1000:1000 bitcoin lightning

That should change the owner of the directories and get you started. Notice however that I haven't updated this project to use the new daemon yet. I'll do that now.