Start an Ark v1 node using a pre-built Ark and customized Postgres image. Current implementation can only be used with mainnet!
- Copy
docker-compose.yml
into your server - Start the DB:
docker-compose up -d db
- Download fresh DB image and restore it:
docker-compose exec -d db make restore
- DO NOT START THE NODE - wait for the database to be fully restored. This can easily take up to 20
minutes, depending on your specs and how many other nodes are downloading the DB image. You can
check if the database is still restoring by checking if
pg_restore
process is running:docker-compose exec db /bin/bash -c 'ps aux | grep pg_restore'
- Start the node:
docker-compose up -d --no-recreate node
- Stop all containers:
docker-compose kill
- Remove database container:
docker-compose rm db
- Restore the database:
docker-compose exec -d db make restore
- DO NOT START THE NODE - wait for the database to be fully restored. This can easily take up to 20
minutes, depending on your specs and how many other nodes are downloading the DB image. You can
check if the database is still restoring by checking if
pg_restore
process is running:docker-compose exec db /bin/bash -c 'ps aux | grep pg_restore'
- Start the node:
docker-compose up -d --no-recreate node
- Restart the node container:
docker-compose restart node
Given the nature of Ark v1 you can't just start the node by running docker-compose up
, this is
because the database needs to be restored before the node gets started. That's why it needs to be
start separately.
- Both arkv1 and postgres images are built by roks0n and are not built automatically on every new update release which can result in an outdated version.
db
container does not have a persistent database.- Despite it's difficult to do so, do not even try running a forging node.
- Current implementation can only be used for mainnet.
- Source code of the rokson/arkv1db image: https://github.com/deadlock-delegate/docker-ark-postgres