Using a Docker Container

Before continuing, please make sure you have setup a Stash and Controller address, as mentioned in the Account Setup section.

Sync Chain Data

Ensure Docker is installed (or install it in your OS of choice) and run the creditcoin-node Docker image.

Docker should automatically pull the specified gluwa/creditcoin image. If not, you can try pulling it yourself from DockerHub by running docker pull gluwa/creditcoin:2.231.0-mainnet and then re-running the command below.

PowerShell does not support comments on multiline commands, please use the uncommented version.

docker run \
 --name creditcoin-validator \
 -p 30333:30333 \
 -v <your local data path>:/creditcoin-node/data  \
 gluwa/creditcoin:2.231.0-mainnet `# Enter latest mainnet image` \
 --name "validator name" `# name the validator` \
 --telemetry-url "wss:// 0" `# (optional) opt in to telemetry` \
 --public-addr "/dns4/<yourhostname or ip>/tcp/30333" `# REPLACE <yourhostname or ip> with the public IP address or host name at which your node can be reached` \
 --chain main `# we want to connect to the mainnet` \
 --bootnodes "/dns4/" "/dns4/" "/dns4/" \
 --validator `# we want to run a validator node` \
 --base-path /creditcoin-node/data `# the base path to store the node's data` \
 --port 30333 # the port to use for node-to-node communication

In the command above, notice the -v flag that takes a local directory as the first part of the parameter. It's import that docker has the ability to write to this directory, otherwise you will see errors such as Error: Service(Client(Backend("IO Error: Permission denied (os error 13)"))). Your command will likely use a path similar to -v /home/validator/data:/creditcoin-node/data.

Here is an example command to run a validator that connects to the Creditcoin Testnet:

docker run \
-p 30333:30333 \
-v ~/chain_data:/data \
gluwa/creditcoin:2.223.0-testnet \
--bootnodes "/dns4/" "/dns4/" "/dns4/" \
--chain test \
--validator \
--base-path /data \
--port 30333

Last updated