nomos-node/deployment

Docker Compose Deployment for Logos Blockchain

The Logos blockchain Docker Compose deployment contains four distinct service types:

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

Building

Run all the docker compose commands below from this deployment/ directory, where the Compose files (compose.yml, compose.run.yml, compose.setup.yml) live.

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

docker compose build

Configuring

Configuration of the Docker deployment is accomplished using an .env file next to compose.yml in this directory. A documented example is in .env.example, and each environment has its own file (.env.devnet, .env.testnet); select one by pointing Compose at it, e.g. docker compose --env-file .env.devnet up, or by copying it to the default .env.

To adjust the count of Logos blockchain nodes, modify the variable:

DOCKER_COMPOSE_LIBP2P_REPLICAS=100

Running

Initiate the deployment 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 logos-blockchain-node

Using deployment

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

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

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

docker compose ps 

Release & deployment file taxonomy

Deployment files fall into three categories by how often they change. This makes it clear which files are reusable blueprints and which must be touched on every release.

Genesis ceremony layout

Genesis ceremony inputs are grouped by environment under deployment/ceremony/genesis/ (env ∈ devnet, testnet, standalone). Per-environment dirs sit next to an optional shared/ dir, so files common to every environment have a natural home:

deployment/ceremony/genesis/
  shared/                         # (optional) inputs common to ALL environments
  <env>/
    inscribe.yaml                 # TEMPLATE entropy + PER-RELEASE chain_id/genesis_time
    deployment-template.yaml      # PER-TYPE consensus / network / blend params
    stakeholders.yaml             # PER-TYPE genesis stake distribution
    providers.yaml                # PER-TYPE bootstrap providers (id, locators)
    faucet.yaml                   # PER-TYPE faucet identity + funds

The per-environment .env files (.env.devnet, .env.testnet) live in deployment/ next to compose.yml, since they are consumed by Docker Compose.

The genesis ceremony (logos-blockchain-tools-genesis ceremony, tools/blockchain-tools/src/bin/genesis.rs) reads all input files in the <env>/ dir and writes a fully-resolved settings file. The generated output (not these inputs) is what the node embeds and what code-check.yml / config tests validate:

Trigger	Inputs	Output (committed)
.github/workflows/genesis-ceremony.yml (devnet / testnet)	deployment/ceremony/genesis/<env>/*	nodes/node/binary/src/config/deployment/settings.yaml
scripts/standalone-genesis-ceremony.sh (local)	deployment/ceremony/genesis/standalone/*	nodes/node/standalone-deployment-config.yaml

1. Template for all deployments (any type)

Shared blueprints reused by every deployment type; not edited per release.

• deployment/compose.yml, deployment/compose.run.yml, deployment/compose.setup.yml, deployment/compose.tracing.yml
• Dockerfile, deployment/Dockerfile
• deployment/cfgsync.yaml, deployment/cfgsync/deployment-settings.yaml
• deployment/nginx/*, deployment/scripts/*, deployment/systemd/*
• the # TEMPLATE section (entropy_sources) of each deployment/ceremony/genesis/<env>/inscribe.yaml

2. Template for a certain deployment type

Per-type blueprints; change only when a network type is re-defined.

• The blueprint files in deployment/ceremony/genesis/<env>/ (deployment-template.yaml, stakeholders.yaml, providers.yaml, faucet.yaml)
• The # DEPLOYMENT TYPE section of .env.<env> (TOOLS_IMAGE_LABEL, EXPLORER_IMAGE_LABEL, ENV_TITLE_STRING, PUBLIC_IP_ADDR, DOCKER_COMPOSE_LIBP2P_REPLICAS, node ports)

3. Per-release info (edited on every release)

• The # PER-RELEASE section (chain_id, genesis_time) of deployment/ceremony/genesis/<env>/inscribe.yaml
• NODE_IMAGE_LABEL in .env.<env> (its # PER-RELEASE section)
• The version input of the genesis ceremony workflow (fills VERSION_PLACEHOLDER)

Generated each release (by the ceremony, not hand-edited): nodes/node/binary/src/config/deployment/settings.yaml, nodes/node/standalone-deployment-config.yaml.