Starting Your Nodes
Prior to starting up your nodes make sure you have the following items completed:
- Bootstrap process completed with the bootstrap directory handy (default:
/var/flow/bootstrap
) - Flow
data
directory created (default:/var/flow/data
) - node config ready
- Firewall exposes TCP/3569, and if you are running
access
node also the GRPC port (default: TCP/9000)
For more details head back to Setting up your node
When you have all the above completed, you can start your Flow node via systemd
or docker
.
systemd​
Ensure that you downloaded the systemd unit file. If you haven't, follow the Set your node to start guide to get your unit file and enabled.
Once you have your Flow service enabled you can now start your service: systemctl start flow
Docker​
If you don't have have systemd on your system, or prefer not to use systemd, you can run the following docker
commands for your respective Flow role to start your node!
Access​
_14docker run --rm \_14 -v /path/to/bootstrap:/bootstrap:ro \_14 -v /path/to/data:/data:rw \_14 --name flow-go \_14 --network host \_14 gcr.io/flow-container-registry/access:v0.0.6-alpha \_14 --nodeid=${FLOW_GO_NODE_ID} \_14 --bootstrapdir=/bootstrap \_14 --datadir=/data/protocol \_14 --rpc-addr=0.0.0.0:9000 \_14 --ingress-addr=${FLOW_NETWORK_COLLECTION_NODE} \_14 --script-addr=${FLOW_NETWORK_EXECUTION_NODE} \_14 --bind 0.0.0.0:3569 \_14 --loglevel=error
Collection​
_13docker run --rm \_13 -v /path/to/bootstrap:/bootstrap:ro \_13 -v /path/to/data:/data:rw \_13 --name flow-go \_13 --network host \_13 gcr.io/flow-container-registry/collection:v0.0.6-alpha \_13 --nodeid=${FLOW_GO_NODE_ID} \_13 --bootstrapdir=/bootstrap \_13 --datadir=/data/protocol \_13 --rpc-addr=0.0.0.0:9000 \_13 --nclusters=${FLOW_NETWORK_COLLECTION_CLUSTER_COUNT} \_13 --bind 0.0.0.0:3569 \_13 --loglevel=error
Consensus​
_12docker run --rm \_12 -v /path/to/bootstrap:/bootstrap:ro \_12 -v /path/to/data:/data:rw \_12 --name flow-go \_12 --network host \_12 gcr.io/flow-container-registry/consensus:v0.0.6-alpha \_12 --nodeid=${FLOW_GO_NODE_ID} \_12 --bootstrapdir=/bootstrap \_12 --datadir=/data/protocol \_12 --nclusters=${FLOW_NETWORK_COLLECTION_CLUSTER_COUNT} \_12 --bind 0.0.0.0:3569 \_12 --loglevel=error
Execution​
_13docker run --rm \_13 -v /path/to/bootstrap:/bootstrap:ro \_13 -v /path/to/data:/data:rw \_13 --name flow-go \_13 --network host \_13 gcr.io/flow-container-registry/execution:v0.0.6-alpha \_13 --nodeid=${FLOW_GO_NODE_ID} \_13 --bootstrapdir=/bootstrap \_13 --datadir=/data/protocol \_13 --ingress-addr=0.0.0.0:9000 \_13 --nclusters=${FLOW_NETWORK_COLLECTION_CLUSTER_COUNT} \_13 --bind 0.0.0.0:3569 \_13 --loglevel=error
Verification​
_12docker run --rm \_12 -v /path/to/bootstrap:/bootstrap:ro \_12 -v /path/to/data:/data:rw \_12 --name flow-go \_12 --network host \_12 gcr.io/flow-container-registry/verification:v0.0.6-alpha \_12 --nodeid=${FLOW_GO_NODE_ID} \_12 --bootstrapdir=/bootstrap \_12 --datadir=/data/protocol \_12 --nclusters=${FLOW_NETWORK_COLLECTION_CLUSTER_COUNT} \_12 --bind 0.0.0.0:3569 \_12 --loglevel=error
Additional Flags​
Networking Layer​
All networking layer settings are initialized to default values from the config/default-config.yml file when the Flow node starts up. Each attribute in this YAML file matches a flag name, allowing you to override the default setting by specifying the corresponding flag in the docker run
command. For instance, to change the networking-connection-pruning
setting, use its matching flag name (networking-connection-pruning
) and desired value in the docker run
command.