nomos-node/testnet
Gusto 5c75c92ff7 tmp: container hostname 2024-12-20 13:35:20 +02:00
..
cfgsync Use metrics endpoint from the cfgsync params 2024-12-20 12:53:38 +02:00
monitoring Predefined dashboard for testnet metrics 2024-12-20 12:54:14 +02:00
scripts tmp: container hostname 2024-12-20 13:35:20 +02:00
Dockerfile Pin prometheus version for otlp functionality 2024-12-20 12:54:04 +02:00
README.md Testnet: Kzgrs config (#797) 2024-10-02 14:26:39 +03:00
cfgsync.yaml Tracing: Otlp metrics (#909) 2024-11-07 04:25:20 +02:00

README.md

Docker Compose Testnet for Nomos

The Nomos Docker Compose Testnet contains four distinct service types:

  • Nomos Node Services: Multiple dynamically spawned Nomos nodes that synchronizes their configuration via cfgsync utility.

Building

Upon making modifications to the codebase or the Dockerfile, the Nomos images must be rebuilt:

docker compose build

Configuring

Configuration of the Docker testnet is accomplished using the .env file. An example configuration can be found in .env.example.

To adjust the count of Nomos nodes, modify the variable:

DOCKER_COMPOSE_LIBP2P_REPLICAS=100

Running

Initiate the testnet by executing the following command:

docker compose up

This command will merge all output logs and display them in Stdout. For a more refined output, it's recommended to first run:

docker compose up -d

Followed by:

docker compose logs -f nomos-node

Using testnet

Bootstrap node is accessible from the host via 3000 and 18080 ports. To expose other nomos nodes, please update nomos-node service in the compose.yml file with this configuration:

  nomos-node-0:
    ports:
    - "3001-3010:3000" # Use range depending on the number of nomos node replicas.
    - "18081-18190:18080"

After running docker compose up, the randomly assigned ports can be viewed with ps command:

docker compose ps