Skip to main content

Deploy Node

Prerequisites​

The drives must already be prepped using the method in this wiki:

Docker should be installed on Ubuntu WSL

Portainer is not required but highly recommended as it provides a nice GUI front end to Docker. Make sure to complete the last section "Keep Ubuntu VM Running"

Resources​

The following are relevant resources:

  1. Port Forwarding (required)
  2. Official Autonomys Wiki

Deploy Autonomys Docker Networks​

For organizational purposes a network will be created for Autonomys docker containers. Right click on the Windows start menu and then select "Terminal". Open Ubuntu with wsl then paste in and execute the following command

sudo docker network create \
  --driver bridge \
  --subnet 172.25.0.0/16 \
  --gateway 172.25.0.1 \
  autonomys-network

This creates a new network called "autonomys-network" with the specified subnet and gateway. Close the Terminal as it is no longer needed.

Alternately, a network can be created via Portainer by selecting "Networks" > "Add Network" and then setting the following values:

  • Name: autonomys-network
  • Driver: bridge
  • Subnet: 172.25.0.0/16
  • Gateway: 172.25.0.1

Then click "Create Network"

Deploy Node​

Open up Portainer, go to "Stacks" and then click "Add Stack"

add-stack

For "Name" enter "autonomys-node". Navigate to the Docker node.yaml then copy the code and paste it into the stack file. Update the following:

  1. image: Update the image to the latest available
  2. --name: Update the name, this is displayed in the telemetry
  3. TZ=: Update this to your own local timezone

Once everything is updated, scroll to the bottom of the page and click "Deploy the stack".

Node Syncing​

The Node will begin to connect to peers and sync with the network. There may not be a lot of progress as first, but eventually a "snap-sync" will occur and a large number of blocks will be synced. It looks something like this in the logs:

2024-10-06T15:05:37.481031Z  INFO Consensus: substrate: ⚙️  Syncing 711748.0 bps, target=#3589832 (6 peers), best: #3558740 (0x123e…cff3), finalized #3558740 (0x123e…cff3), ⬇ 219.0kiB/s ⬆ 2.0kiB/s

Note that it may take some time (10-20 minutes) to occur. You may also see errors/warns such as, which can be safely ignored:

2024-10-20T20:06:52.675325Z  WARN Consensus: telemetry: ❌ Error while dialing /dns/telemetry.subspace.network/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }

The most common log file that you will see is something like this:

2024-10-06T15:00:57.441368Z  INFO Consensus: substrate: ⚙️  Syncing  0.0 bps, target=#3589783 (4 peers), best: #0 (0x0c12…1c34), finalized #0 (0x0c12…1c34), ⬇ 13.5kiB/s ⬆ 3.9kiB/s
  • Syncing 0.0 bps - This is normal at first and we should see it increase
  • target=#3589783 - This is the current block height, and will increase.
  • (4 peers) - Current peers. This should eventually increase to 40
  • best: #0 - Our current synced blocks, this will eventually need to reach the target