ofawx Posted August 26, 2021 Share Posted August 26, 2021 (edited) OFAWX/DOCKER-TEMPLATES Support thread for my Docker templates. Let me know of any issues and will get back ASAP. Please share at minimum: Which container it is you're having issues Full logs since startup for that container The container config, with any private details redacted Current supported containers: bitcoind Don't trust, verify! A full Bitcoin Core node to maintain your autonomy Based on trustless docker-bitcoind electrs A lightweight personal Electrum server Based on docker-electrs electrumx A high-performing Electrum server Based on docker-electrumx Edited September 8, 2021 by ofawx Add electrumx Quote Link to comment
ofawx Posted August 26, 2021 Author Share Posted August 26, 2021 (edited) FAQ Should I use ElectrumX or electrs? ElectrumX is a high-performance server appropriate for serving many clients, including yourself and optionally the wider public. It is faster (<1 second responses), but consumes more resources. electrs is a low-footprint server that is appropriate for personal use or with a small number of trusted friends. Requests are served more slowly (3+ seconds), but the server consumes fewer resources. Or run both! I run a public ElectrumX server to support the network, and retain a personal electrs server to ensure uptime and privacy for myself. Edited September 8, 2021 by ofawx Add FAQ Quote Link to comment
Robc390 Posted August 31, 2021 Share Posted August 31, 2021 I am trying this out. how to i connect to a wallet? I used the bitcoin website to find a windows based wallet, Electrum. the wallet is setup, so I need to do something with the bitcoin.conf file? Quote Link to comment
ofawx Posted August 31, 2021 Author Share Posted August 31, 2021 11 hours ago, Robc390 said: I am trying this out. how to i connect to a wallet? I used the bitcoin website to find a windows based wallet, Electrum. the wallet is setup, so I need to do something with the bitcoin.conf file? It's unfortunately not possible to connect Electrum directly to Bitcoin Core (bitcoind). Bitcoin Core has a built-in wallet, but without a GUI here it is unwieldy to use. I hope to release container templates soon implementing both ElectrumX and electrs servers. These connect to Bitcoin Core via the RPC interface, and serve Electrum clients. I can update you here when these become available. Quote Link to comment
Robc390 Posted September 1, 2021 Share Posted September 1, 2021 1 hour ago, ofawx said: It's unfortunately not possible to connect Electrum directly to Bitcoin Core (bitcoind). Bitcoin Core has a built-in wallet, but without a GUI here it is unwieldy to use. I hope to release container templates soon implementing both ElectrumX and electrs servers. These connect to Bitcoin Core via the RPC interface, and serve Electrum clients. I can update you here when these become available. Thanks. Next question then is what are the wallets keys, i should be able to check it on the blockchain (bscscan.com?). I'll keep an eye here for updates. Quote Link to comment
ofawx Posted September 3, 2021 Author Share Posted September 3, 2021 On 9/1/2021 at 11:21 AM, Robc390 said: Thanks. Next question then is what are the wallets keys, i should be able to check it on the blockchain (bscscan.com?). I'll keep an eye here for updates. Just published electrs to Community Apps. Give it a go and feel free to let me know if you encounter any issues. Quote Link to comment
Marshalleq Posted September 8, 2021 Share Posted September 8, 2021 Hi there, I'm getting Execution Error, Bad Data and really it's quite a simple container isn't it. Anything obvious I'm missing? Thanks. Quote Link to comment
ofawx Posted September 8, 2021 Author Share Posted September 8, 2021 6 hours ago, Marshalleq said: Hi there, I'm getting Execution Error, Bad Data and really it's quite a simple container isn't it. Anything obvious I'm missing? Thanks. It sounds more like a Docker error than a container error to be honest, but happy to have a look. Could you share: Which container it is you're having issues Full logs since startup for that container The container config, with any private details redacted of course. Cheers Quote Link to comment
Unrea1 Posted September 16, 2021 Share Posted September 16, 2021 Hi, I tried to install the bitcoind Docker via Community Applications. Upton starting the Docker I get: Execution error Bad parameter Unraid generates this Docker command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='bitcoind' --net='bridge' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -p '8333:8333/tcp' -p '8332:8332/tcp' -v '/mnt/user/bitcoin/core/':'/root/.bitcoin/':'rw' 'ofawx/bitcoind' -txindex 6ef94ee974f0078f7e787458a30aac5b030c4a5e21bf664bd1a9bc4caaf20e46 The command finished successfully! Quote Link to comment
pelux Posted September 16, 2021 Share Posted September 16, 2021 The bitcoind container fails to start with the default settings in the template. Something to do with the txindex parameter. Attempting to starting the container throws this error in the Unraid GUI. The container will start if "-txindex" is removed from the Post Arguments in the template. 1 Quote Link to comment
ofawx Posted September 16, 2021 Author Share Posted September 16, 2021 9 hours ago, pelux said: The container will start if "-txindex" is removed from the Post Arguments in the template. Thanks for the quick debug! Not sure why this suddenly stopped working but have removed it from the default config, which will appear in CA in the next few hours. If txindex is required (which is for my Electrum server containers for example), please add it manually in your bitcoin.conf file. Quote Link to comment
Anadoliev Posted October 11, 2021 Share Posted October 11, 2021 Hi, I’m starting to get some more information about crypto currencies. Bitcoind is it part of the lightning network? Quote Link to comment
GG73 Posted October 21, 2021 Share Posted October 21, 2021 hi, having difficulty uninstalling. can uninstall from docker page and uninstalls correctly with no errors but I still have a bitcoin folder in my shares that i cannot delete. Any help is appreciated, thank you. Quote Link to comment
ofawx Posted October 22, 2021 Author Share Posted October 22, 2021 14 hours ago, GG73 said: hi, having difficulty uninstalling. can uninstall from docker page and uninstalls correctly with no errors but I still have a bitcoin folder in my shares that i cannot delete. Any help is appreciated, thank you. Hi, how are you deleting it and is there an error or a message when you try? If it is in its own share, it should be straightforward to delete from the Unraid GUI. If there is still invisible data in the share, use the command line to delete everything in the share like this: $ rm -rf /mnt/user/share/bitcoind/* and then delete the share from the GUI. Be careful with the above command, it will delete everything specified without confirming! If it is a folder within another share, you can use the same command above like: $ rm -rf /mnt/user/myshare/some/folder/bitcoind but again, be sure to specify the correct folder as there is no undo. Quote Link to comment
GG73 Posted October 23, 2021 Share Posted October 23, 2021 Thank you. I managed to delete using krusader in the end Quote Link to comment
VaartEx Posted May 11, 2023 Share Posted May 11, 2023 (edited) Hi ofawx Do you still support electrs and electrumx? I could use some help with installation since I don't fully understand what's happening behind the curtains. (I'm one of those annoying people that "needs to know before doing") What's the relationship between bitcoind, electrs and electrumx? Guidance is much appreciated =) Edited May 12, 2023 by VaartEx Quote Link to comment
Tabaffo Posted February 11 Share Posted February 11 Hi! Tnx for your job! I'm trying to run it under tor, is my first time with an node, so I'm a newbie. If I've understood right i've only to put the setting in my bitcoin.conf, right? Mine is like this: printtoconsole=1 # Only connect to peers via Tor. onlynet=onion But if I try to start the node I've this logs: 2024-02-11T11:43:53Z Bitcoin Core version v26.0 (release build) 2024-02-11T11:43:53Z InitParameterInteraction: parameter interaction: -onlynet excludes IPv4 and IPv6 -> setting -dnsseed=0 2024-02-11T11:43:53Z Using the 'x86_shani(1way,2way)' SHA256 implementation 2024-02-11T11:43:53Z Using RdSeed as an additional entropy source 2024-02-11T11:43:53Z Using RdRand as an additional entropy source 2024-02-11T11:43:53Z Default data directory /root/.bitcoin 2024-02-11T11:43:53Z Using data directory /root/.bitcoin 2024-02-11T11:43:53Z Config file: /root/.bitcoin/bitcoin.conf 2024-02-11T11:43:53Z Config file arg: onlynet="onion" 2024-02-11T11:43:53Z Config file arg: printtoconsole="1" 2024-02-11T11:43:53Z Command-line arg: printtoconsole="" 2024-02-11T11:43:53Z Using at most 125 automatic connections (40960 file descriptors available) 2024-02-11T11:43:53Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements 2024-02-11T11:43:53Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements 2024-02-11T11:43:53Z Script verification uses 11 additional threads 2024-02-11T11:43:53Z scheduler thread start 2024-02-11T11:43:53Z Binding RPC on address ::1 port 8332 2024-02-11T11:43:53Z [libevent:warning] getaddrinfo: no address associated with nodename 2024-02-11T11:43:53Z Binding RPC on address ::1 port 8332 failed. 2024-02-11T11:43:53Z Binding RPC on address 127.0.0.1 port 8332 2024-02-11T11:43:53Z [http] creating work queue of depth 16 2024-02-11T11:43:53Z Using random cookie authentication. 2024-02-11T11:43:53Z Generated RPC authentication cookie /root/.bitcoin/.cookie 2024-02-11T11:43:53Z [http] starting 4 worker threads 2024-02-11T11:43:53Z Using wallet directory /root/.bitcoin 2024-02-11T11:43:53Z init message: Verifying wallet(s)… 2024-02-11T11:43:53Z Using /16 prefix for IP bucketing 2024-02-11T11:43:53Z init message: Loading P2P addresses… 2024-02-11T11:43:53Z Loaded 1883 addresses from peers.dat 7ms 2024-02-11T11:43:53Z init message: Loading banlist… 2024-02-11T11:43:53Z SetNetworkActive: true 2024-02-11T11:43:53Z Cache configuration: 2024-02-11T11:43:53Z * Using 2.0 MiB for block index database 2024-02-11T11:43:53Z * Using 8.0 MiB for chain state database 2024-02-11T11:43:53Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space) 2024-02-11T11:43:53Z init message: Loading block index… 2024-02-11T11:43:53Z Assuming ancestors of block 00000000000000000001a0a448d6cf2546b06801389cc030b2b18c6491266815 have valid signatures. 2024-02-11T11:43:53Z Setting nMinimumChainWork=000000000000000000000000000000000000000052b2559353df4117b7348b64 2024-02-11T11:43:53Z Opening LevelDB in /root/.bitcoin/blocks/index 2024-02-11T11:43:54Z Opened LevelDB successfully 2024-02-11T11:43:54Z Using obfuscation key for /root/.bitcoin/blocks/index: 0000000000000000 2024-02-11T11:43:54Z LoadBlockIndexDB: last block file = 0 2024-02-11T11:43:54Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03) 2024-02-11T11:43:54Z Checking all blk files are present... 2024-02-11T11:43:54Z Initializing chainstate Chainstate [ibd] @ height -1 (null) 2024-02-11T11:43:54Z Opening LevelDB in /root/.bitcoin/chainstate 2024-02-11T11:43:54Z Opened LevelDB successfully 2024-02-11T11:43:54Z Using obfuscation key for /root/.bitcoin/chainstate: 06805bf65eaf887c 2024-02-11T11:43:54Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831a934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000 2024-02-11T11:43:54Z Opening LevelDB in /root/.bitcoin/chainstate 2024-02-11T11:43:55Z Opened LevelDB successfully 2024-02-11T11:43:55Z Using obfuscation key for /root/.bitcoin/chainstate: 06805bfa5edf887c 2024-02-11T11:43:55Z [Chainstate [ibd] @ height 0 (000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f)] resized coinsdb cache to 8.0 MiB 2024-02-11T11:43:55Z [Chainstate [ibd] @ height 0 (000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f)] resized coinstip cache to 440.0 MiB 2024-02-11T11:43:55Z init message: Verifying blocks… 2024-02-11T11:43:55Z block index 2117ms 2024-02-11T11:43:55Z Setting NODE_NETWORK on non-prune mode 2024-02-11T11:43:55Z block tree size = 1 2024-02-11T11:43:55Z nBestHeight = 0 2024-02-11T11:43:55Z initload thread start 2024-02-11T11:43:55Z torcontrol thread start 2024-02-11T11:43:55Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast 2024-02-11T11:43:55Z Bound to 127.0.0.1:8334 2024-02-11T11:43:55Z initload thread exit 2024-02-11T11:43:55Z Bound to [::]:8333 2024-02-11T11:43:55Z Bound to 0.0.0.0:8333 2024-02-11T11:43:55Z Loaded 0 addresses from "anchors.dat" 2024-02-11T11:43:55Z 0 block-relay-only anchors will be tried for connections. 2024-02-11T11:43:55Z init message: Starting network threads… 2024-02-11T11:43:55Z DNS seeding disabled 2024-02-11T11:43:55Z net thread start 2024-02-11T11:43:55Z opencon thread start 2024-02-11T11:43:55Z addcon thread start 2024-02-11T11:43:55Z msghand thread start 2024-02-11T11:43:55Z init message: Done loading And after hours I've this message: Potential stale tip detected, will try using extra outbound peer (last tip update: Do I have to install Tor separately? I've tried to install it (using obfs4-bridge) but I think this is a relay node not the thing I need to use the normal tor. At the end, If I try to run the node without bitcoin.conf all run very well, I see downloading blocks in the logs, so, for sure is a tor problem. I only want to run the node without make it public I'm running it. Any advice? help? tnx! Quote Link to comment
Aaldorabi Posted March 5 Share Posted March 5 ```Config { network: Bitcoin, db_path: "./db/bitcoin", daemon_dir: "/data/.bitcoin", daemon_auth: CookieFile("/data/.bitcoin/.cookie"), daemon_rpc_addr: V4(192.168.1.1:8332), daemon_p2p_addr: V4(127.0.0.1:8333), electrum_rpc_addr: V4(0.0.0.0:50001), monitoring_addr: V4(127.0.0.1:4224), wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: Some(200), auto_reindex: true, ignore_mempool: false, sync_once: false, server_banner: "Welcome to electrs 0.9.0 (Electrum Rust Server)!", args: [] } [2024-03-05T18:36:02.061Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224 [2024-03-05T18:36:02.062Z DEBUG tiny_http] Server listening on 127.0.0.1:4224 Error: failed to open DB: ./db/bitcoin Caused by: Failed to create RocksDB directory: `Os { code: 13, kind: PermissionDenied, message: "Permission denied" }`. [2024-03-05T18:36:02.063Z DEBUG tiny_http] Running accept thread``` I keep getting this error in my unraid logs for electrs, im trying to set it up for Bitcoind for wallet Quote Link to comment
jquery Posted April 26 Share Posted April 26 (edited) On 3/5/2024 at 8:02 PM, Aaldorabi said: ```Config { network: Bitcoin, db_path: "./db/bitcoin", daemon_dir: "/data/.bitcoin", daemon_auth: CookieFile("/data/.bitcoin/.cookie"), daemon_rpc_addr: V4(192.168.1.1:8332), daemon_p2p_addr: V4(127.0.0.1:8333), electrum_rpc_addr: V4(0.0.0.0:50001), monitoring_addr: V4(127.0.0.1:4224), wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: Some(200), auto_reindex: true, ignore_mempool: false, sync_once: false, server_banner: "Welcome to electrs 0.9.0 (Electrum Rust Server)!", args: [] } [2024-03-05T18:36:02.061Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224 [2024-03-05T18:36:02.062Z DEBUG tiny_http] Server listening on 127.0.0.1:4224 Error: failed to open DB: ./db/bitcoin Caused by: Failed to create RocksDB directory: `Os { code: 13, kind: PermissionDenied, message: "Permission denied" }`. [2024-03-05T18:36:02.063Z DEBUG tiny_http] Running accept thread``` I keep getting this error in my unraid logs for electrs, im trying to set it up for Bitcoind for wallet this error seems to be caused by the fact that the ./db/bitcoin directory can't be created. I solved that by manually creating the directory inside the electrs folder. After that electrs could't access the auth-cookie in the bitcoin-node directory, because the permissions were jumbled. I fixed that by changing the permissions. annoyingly, the permissions are reset every time I restart the bitcoin docker. But even after all that electrs can't connect to the RPC service of bitcoind. No matter what I try, I get a "connection refused" error. I am at my wits end. And since there does not seem to be any kind of support here, I am ready to give up. edit: I solved the last bit: The problem was, that the bitcoin RPC service is only listening on localhost by default. I couldn't figure out how to change that, unfortunately, because I couldn't figure out how to pass "-rpcallowip" when the docker starts. Instead, I changed the network to "host" in the settings of the bitcoin docker and the electrs docker. Now they are listening on the same IP and the localhost connection works. Now I only need to find a way to automatically change the permissions on the .cookie file each time the bitcoin docker restarts.# Finally, I am not sure, if its a good idea to run v0.9 of electrs when 0.10.4 is already out. Edited April 26 by jquery Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.