-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shesek/lightning-charge:standalone - unable to start #68
Comments
It seems like lightning charge was unable to find the c-lightning rpc socket in Lightning charge should normally wait for the c-lightning socket file to appear if its not there when starting up (to support starting charge while c-lightning is still warming up), but there was a bug preventing this from working, which was causing the error you were seeing. 43973f4 should fix this, I'll be releasing this in v0.4.12 soon. |
0.4.12 is released and available on docker hub, can you try again and verify this fixed the issue? |
thank you! I managed to move on slightly.. but there is still a problem.. This is the output from container startup: Using lightningd directory mounted in /etc/lightning... SyntaxError: Unexpected end of JSON input Maybe I'm doing something fundamentally wrong.. |
Which version of c-lightning are you running? Also, note that you don't need to mount in the bitcoin's datadir if you're mounting lightning's. |
v.0.7.0 I need to say that this containers are running on top of NAS from QNAP and I'm mounting the file-system of c-lightning as a share: am I able to turn some level of debug logging via Environment-params ? maybe I can find out more that way.. |
I'm not aware of any specific issues that should prevent charge from working with c-lightning v0.7.0, but would it be possible to update to the latest version (v0.7.3) and see if the issue persists? There were lots of major improvements and bug fixes since v0.7.0, so you should probably update anyway :) |
It works! :) curl $CHARGE/info @shesek, thank you so much for your support and your effort.. I'm happy to join your LN node.. you can find me at: 02ca4c46faa50b2d961f4ad2e9d00c90826077b6a282b71079a88cb29a34b8c84a@178.143.52.84:9735 issue can be closed. Cheers! |
@jaro2k I'm trying to do this as well. Is there any chance you'd share your docker-compose.yml? Any help much appreciated |
I'm searching for advise..
I'm running bitcoin node and c-lightning in separate containers and I'm trying to get them integrated with lightning-charge running in third container.
All 3 containers are on the same host.
following the document from this project I have mapped:
/etc/lightning -> /root/.lightning
and I mounted /root/.lightning file-system from c-lightning container to the lightning-charge container.
When container starts it throws the following error:
Using lightningd directory mounted in /etc/lightning... waiting for RPC unix socket... bin/docker-entrypoint.sh: line 71: inotifywait: command not found
Starting Lightning Charge
Lightning client connection error { Error: connect ENOENT /etc/lightning/lightning-rpc
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'connect',
address: '/etc/lightning/lightning-rpc' }
events.js:183
throw er; // Unhandled 'error' event
^
Error: connect ENOENT /etc/lightning/lightning-rpc
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
The text was updated successfully, but these errors were encountered: