vvzvlad/allora
1
0
Fork 0
Code Pull Requests Packages Releases Activity

Fix docker-compose setup setps

Browse Source
This commit is contained in:
conache 2024-03-07 14:13:50 +02:00
parent aaeac27243
commit ce785bb99f
No known key found for this signature in database
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -42,7 +42,6 @@ The current `docker-compose.yml` file shows the `worker` service setting UID and
# Docker-Compose Setup # Docker-Compose Setup
A full working example is provided in the `docker-compose.yml` file. A full working example is provided in the `docker-compose.yml` file.
## Setup
1. **Generate keys**: Create a set of keys for your head and worker nodes. These keys will be used in the configuration of the head and worker nodes. 1. **Generate keys**: Create a set of keys for your head and worker nodes. These keys will be used in the configuration of the head and worker nodes.
**Create head keys:** **Create head keys:**
@ -57,14 +56,14 @@ docker run -it --entrypoint=bash -v ./worker-data:/data 696230526504.dkr.ecr.us-
Important note: If no keys are specified in the volumes, new keys will be automatically created inside `head-data/keys` and `worker-data/keys` when first running step 4. Important note: If no keys are specified in the volumes, new keys will be automatically created inside `head-data/keys` and `worker-data/keys` when first running step 4.
3. **Connect the worker node to the head node**: 2. **Connect the worker node to the head node**:
At this step, both worker and head nodes identities are generated inside `head-data/keys` and `worker-data/keys`. At this step, both worker and head nodes identities are generated inside `head-data/keys` and `worker-data/keys`.
To instruct the worker node to connect to the head node: To instruct the worker node to connect to the head node:
- get the head node's peer_id specified in the `head-data/keys/identity` file - get the head node's peer_id specified in the `head-data/keys/identity` file
- use the peer_id to replace the `head-id` placeholder value specified inside the docker-compose.yml file when running the worker service: `--boot-nodes=/ip4/172.22.0.100/tcp/9010/p2p/{head-id}` - use the peer_id to replace the `head-id` placeholder value specified inside the docker-compose.yml file when running the worker service: `--boot-nodes=/ip4/172.22.0.100/tcp/9010/p2p/{head-id}`
4. **Run setup** 3. **Run setup**
Once all the above is set up, run `docker compose up head worker inference` Once all the above is set up, run `docker compose up head worker inference`
This will bring up the head, the worker and the inference nodes (which will run an initial update). The `updater` node is a companion for updating the inference node state and it's meant to hit the /update endpoint on the inference service. It is expected to run periodically, being crucial for maintaining the accuracy of the inferences. This will bring up the head, the worker and the inference nodes (which will run an initial update). The `updater` node is a companion for updating the inference node state and it's meant to hit the /update endpoint on the inference service. It is expected to run periodically, being crucial for maintaining the accuracy of the inferences.