--- Day changed Fri Aug 10 2018 00:35 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 01:52 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 01:54 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 02:58 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-wrfwhoogjuliwell] has joined #c-lightning 03:12 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 03:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 05:27 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-wrfwhoogjuliwell] has quit [Quit: Connection closed for inactivity] 05:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 05:35 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 06:38 -!- sipicz [5ab50eac@gateway/web/freenode/ip.90.181.14.172] has joined #c-lightning 06:40 < sipicz> Hello everyone, I am trying to setup development environment for btcpayserver. I already have testnet instance running on WS2016 server. Since btcpayserver implements clightning and there is so far now way to run clightning on Windows Server, is it possible to run clightning in docker and connect it to bitcoind which is running on the host (Windows Server)? 06:51 <@cdecker> Hi sipicz, that should be possible, bitcoind can run somewhere else and c-lightning can be told with the --bitcoin-rpcconnect option where to connect to (but still needs bitcoin-cli to be available on the local machine) 06:52 <@cdecker> Nicolas also wrote a socat script in the docker image to expose the unix socket over TCP, so you should be able to talk to it once it is running 06:55 < sipicz> That's perfect, thanks alot for advice. 06:55 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 240 seconds] 07:01 < molz> now we can run c-lightning on windows? 07:06 < sipicz> Yes, let me test it, I will try to write reference after that. 07:07 < molz> oh cool, thanks 07:19 -!- sipicz [5ab50eac@gateway/web/freenode/ip.90.181.14.172] has quit [Ping timeout: 252 seconds] 07:58 -!- ken2812221 [~User@1.200.203.30] has quit [Ping timeout: 240 seconds] 08:38 -!- sipicz [~sipicz@172.14.broadband14.iol.cz] has joined #c-lightning 08:38 -!- sipicz [~sipicz@172.14.broadband14.iol.cz] has quit [Client Quit] 08:40 -!- sipicz [~sipicz@172.14.broadband14.iol.cz] has joined #c-lightning 08:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 08:42 -!- sipicz [~sipicz@172.14.broadband14.iol.cz] has quit [Client Quit] 08:49 -!- sipicz [~sipicz@172.14.broadband14.iol.cz] has joined #c-lightning 08:55 -!- sipicz [~sipicz@172.14.broadband14.iol.cz] has quit [Ping timeout: 260 seconds] 08:55 -!- sipicz_ [~sipicz@58.234.202.74] has joined #c-lightning 08:57 < sipicz_> I am trying to connect lightning that is inside docker to bitcoind on host machine, but it cannot find with this command: 08:57 < sipicz_> lightningd --bitcoin-rpcconnect=bitcoind --bitcoin-rpcuser=test --bitcoin-rpcpassword=1234 --network=testnet --alias=myawesomenode --log-level=debug --bitcoin-rpcport=18333 08:59 < sipicz_> Lightningd says bitcoind is not running, could someone please help me? 09:00 < sipicz_> Bitcoind on host machine is run as following: 09:00 < sipicz_> bitcoind -server -rpcuser=test -rpcpassword=1234 -datadir="D:\BitcoinCoreData" -printtoconsole -testnet 09:02 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-gcaemxermpnearcg] has joined #c-lightning 09:53 -!- sipicz_ [~sipicz@58.234.202.74] has quit [Read error: Connection reset by peer] 10:32 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 11:10 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-ryqvlmtgbyuajtyz] has joined #c-lightning 11:11 < blockstream_bot> [Christian Decker, Blockstream] Wait, no, c-lightning cannot run on Windows. But if you have bitcoind on windows, then lightningd can connect to it 11:11 < blockstream_bot> [Christian Decker, Blockstream] (if you run docker images on Windows they are running in VMS) 11:13 < blockstream_bot> [Christian Decker, Blockstream] bitcoind needs to be started with rpcallowip to allow access from docker, and lightningd needs to be started with --bitcoin-rpcconnect=hostip so it can connect to bitcoind 11:48 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 12:08 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1] 12:14 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 256 seconds] 12:16 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-gcaemxermpnearcg] has quit [Quit: Connection closed for inactivity] 12:18 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 12:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:28 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 12:32 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 13:12 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 240 seconds] 13:15 -!- grubles [~grubles@unaffiliated/grubles] has quit [Ping timeout: 240 seconds] 13:18 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection reset by peer] 13:25 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 13:25 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 13:45 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning 14:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 15:18 -!- ken2812221 [~User@1.200.203.30] has joined #c-lightning 17:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 17:06 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 17:07 -!- farmerwampum [~farmerwam@104.129.28.58] has quit [Ping timeout: 256 seconds] 17:15 < roasbeef> could possibly try the WLS i guess 17:17 < molz> WLS is linux on windows, better than a Linux VM.. I tried c-lightning on WLS before but for some reason the node never got caught up to the same height with bitcoind. WLS is not really a stable environment 17:18 < molz> i mean not* better than a Linux VM 17:19 < molz> i think WLS is more an environment to build stuff but not to run stuff 18:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 20:15 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds] 20:58 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 21:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 21:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 21:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds]