Skip to content

Run

OS Requirements⚓︎

Use Cases⚓︎

  • Pool Management
  • Wallet Management
  • Node testing
docker run --init -dit
--name <YourCName>
--security-opt=no-new-privileges
-e NETWORK=mainnet
-v <your_custom_path>:/opt/cardano/cnode/priv
-v <your_custom_db_path>:/opt/cardano/cnode/db
cardanocommunity/cardano-node

Use Cases:⚓︎

  • Node Relay
docker run --init -dit
--name <YourCName>
--security-opt=no-new-privileges
-e NETWORK=mainnet
-p 6000:6000
-v <your_custom_path>:/opt/cardano/cnode/priv
-v <your_custom_db_path>:/opt/cardano/cnode/db
cardanocommunity/cardano-node
  • Node Relay with custom permanent cfg by passing the env variable CONFIG (Mapping your configuration folder as below will allow you to retain configurations if you update or delete your container)
docker run --init -dit
--name <YourCName>
--security-opt=no-new-privileges
-e NETWORK=mainnet
-e CONFIG=/opt/cardano/cnode/priv/<your own configuration files>.yml
-p 6000:6000
-v <your_custom_path>:/opt/cardano/cnode/priv
-v <your_custom_db_path>:/opt/cardano/cnode/db
cardanocommunity/cardano-node

Note

1) --entrypoint=bash # This option won't start the node's container but only the OS running (the node software wont actually start, you'll need to manually execute entrypoint.sh ), ready to get in (trough the command docker exec -it < container name or hash > /bin/bash) and play/explore around with it in command line mode. 2) all guild tools env variable can be used to start a new container using custom values by using the "-e" option. 3) CPU and RAM and SHared Memory allocation option for the container can be used when you start the container (i.e. --shm-size or --memory or --cpus official docker resource docs)