Skip to content

Latest commit

 

History

History
118 lines (99 loc) · 5.58 KB

README.md

File metadata and controls

118 lines (99 loc) · 5.58 KB

docker_nodes

running bitcoind

Configuration file bitcoin.conf should be placed in the data directory before spinning up the container.

docker run --rm -d -p 8332:8332 -p 8333:8333 -v <LOCAL_DATA_DIR_PATH>:/home/bitcoin/.bitcoin --name bitcoind nandubatchu/bitcoind:0.22.0

running bitcoind (bitcoin_abc)

Configuration file bitcoin.conf should be placed in the data directory before spinning up the container.

docker run --rm -d -p 8332:8332 -p 8333:8333 -v <LOCAL_DATA_DIR_PATH>:/home/bitcoinabc/.bitcoinabc --name bitcoinabc nandubatchu/bitcoinabc:0.22.7

running bchn (bitcoin_cash_node)

Configuration file bitcoin.conf should be placed in the data directory before spinning up the container.

docker run --rm -d -p 8332:8332 -p 8333:8333 -v <LOCAL_DATA_DIR_PATH>:/home/bitcoinabc/.bitcoinabc --name bchn nandubatchu/bchn:0.22.7

running bitcoind (bitcoin_sv)

Configuration file bitcoin.conf should be placed in the data directory before spinning up the container.

docker run --rm -d -p 8332:8332 -p 8333:8333 -v <LOCAL_DATA_DIR_PATH>:/home/bitcoinsv/.bitcoinsv --name bitcoinsv nandubatchu/bitcoinsv:1.0.1

running bitcoind (bitcoin_gold)

Configuration file bitcoingold.conf should be placed in the data directory before spinning up the container.

docker run --rm -d -p 8332:8332 -p 8333:8333 -v <LOCAL_DATA_DIR_PATH>:/home/bitcoingold/.bitcoingold --name bgoldd nandubatchu/bgoldd:0.15.2

running litecoind

Configuration file litecoin.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 9332:9332 -p 9333:9333 -v <LOCAL_DATA_DIR_PATH>:/home/litecoin/.litecoin --name litecoind nandubatchu/litecoind:0.17.1

running parity

Need to create a config.toml inside the data directory before spinning up the container. Would require to allow RPC to communicate with the node. (Reference: https://paritytech.github.io/parity-config-generator/)

docker run --rm -d -p 8545:8545 -p 30303:30303 -v <LOCAL_DATA_DIR_PATH>:/home/ethereum/parity_data --name parity nandubatchu/parity-ethereum:latest

running monero-wallet-rpc

Need to create a monero-wallet-cli.conf inside the data directory before spinning up the container. Also would need to generate the wallet files using the monero-wallet-cli and be placed in the /wallet-dir path under the data directory to be accessed by the RPC commands.

docker run --rm -d -p 18088:18088 -v <LOCAL_DATA_DIR_PATH>:/home/monero/.bitmonero --name monero-waller-rpc nandubatchu/monero-wallet-rpc:0.17.1.7

running monerod

Need to create a monerod.conf inside the data directory before spinning up the container.

docker run --rm -d -p 18080:18080 -p 18081:18081 -v <LOCAL_DATA_DIR_PATH>:/home/monero/.bitmonero --name monerod nandubatchu/monerod:0.17.1.7

running dogecoind

Configuration file dogecoin.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 22555:22555 -p 22556:22556 -v <LOCAL_DATA_DIR_PATH>:/home/dogecoin/.dogecoin --name dogecoind nandubatchu/dogecoind:1.14.3

running zcashd

Configuration file zcash.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 8232:8232 -p 8233:8233 -v <LOCAL_DATA_DIR_PATH>:/home/zcash/.zcash --name zcashd nandubatchu/zcashd:4.4.1

running qtumd

Configuration file qtum.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 3888:3888 -p 3889:3889 -v <LOCAL_DATA_DIR_PATH>:/home/qtum/.qtum --name qtumd nandubatchu/qtumd:0.19.1

running dcrd

Configuration file dcrd.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 9108:9108 -p 9109:9109 -v <LOCAL_DATA_DIR_PATH>:/root/.dcrd --name dcrd nandubatchu/dcrd:1.5.1

running dcwallet

Configuration file dcrwallet.conf should be placed in the data directory before spinning up the container

  • To connect to the dcrd instance, we need to place the rpc.cert file of dcrd instance inside the Data directory as dcrd.cert
docker run --rm -d -p 9110:9110 -v <LOCAL_DATA_DIR_PATH>:/root/.dcrwallet --name dcrwallet nandubatchu/dcrwallet:1.5.1

running dashd

Configuration file dash.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 9998:9998 -p 9999:9999 -v <LOCAL_DATA_DIR_PATH>:/home/dashcore/.dashcore --name dashd nandubatchu/dashd:0.16.1.1

running ravend

Configuration file raven.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 8766:8766 -p 8767:8767 -v <LOCAL_DATA_DIR_PATH>:/home/raven/.raven --name ravend nandubatchu/ravend:4.1.0.0

running zelcashd

Configuration file zelcash.conf should be placed in the data directory before spinning up the container

  • requires to change the directory ownership to user 999 (chown -R 999 <LOCAL_DATA_DIR_PATH>)
docker run --rm -d -p 16124:16124 -p 16125:16125 -v <LOCAL_DATA_DIR_PATH>:/home/zelcash/.zelcash --name zelcashd nandubatchu/zelcashd:5.0.0

running rskj

Configuration file node.conf should be placed in the data directory before spinning up the container

docker run --rm -d -p 4444:4444 -p 5050:5050 -v <LOCAL_DATA_DIR_PATH>:/var/lib/rsk --name rskj nandubatchu/rskj:2.0.1

running digibyted

Configuration file digibyte.conf should be placed in the data directory before spinning up the container.

docker run --rm -d -p 12024:12024 -p 14022:14022 -v <LOCAL_DATA_DIR_PATH>:/home/digibyte/.digibyte --name digibyted nandubatchu/digibyted:7.17.2