This allows for easy orchestration of the Midnight Node service.
- Install Docker Engine
- Install Docker Compose
- Install direnv
-
Clone repository
-
In
.envrcset CFG_PRESET to be the environment you wish to point to. Available options:qanet- QA networktestnet-02- TestNet 02preview- Preview network
-
run
direnv allowto load the environment variables -
Run
docker-compose up
The .envrc file will automatically create random secrets and save them as postgres.secret (database password), midnight-node.secret (node private key), and indexer.secret (indexer app secret).
All services are defined in a single compose.yml file. Use Docker Compose profiles to control which services run:
Available profiles:
- (no profile) - Midnight Node only
cardano- Adds Cardano stack (cardano-node, postgres, cardano-db-sync) and Indexer with GraphQL API athttp://localhost:8088ogmios- Adds Ogmios service athttp://localhost:1337proof-server- Adds local Proof Server athttp://localhost:6300
Usage examples:
Run Midnight Node only:
docker compose up -dRun Midnight Node + Cardano stack + Indexer:
docker compose --profile cardano up -dRun with Cardano stack + Ogmios:
docker compose --profile cardano --profile ogmios up -dRun everything (Cardano + Ogmios + Proof Server):
docker compose --profile cardano --profile ogmios --profile proof-server up -d🚀 That's it.
If you're using midnight-node smartcontract or midnight-node wizards that need ogmios, and you're running midnight-node in docker you must pass -O ws://host.docker.internal:1337 as an argument.
(Once PartnerChains 1.7+ is released OGMIOS_URL env var can be set so that it just works, but for now you have to pass it as an argument.)
To restart from fresh, run:
docker compose --profile cardano --profile ogmios --profile proof-server down -v
docker compose --profile cardano --profile ogmios --profile proof-server kill
rm -R ./cardano-data
docker volume rm midnight-node-docker_midnight-data-testnetIf you get warnings like this then likely direnv is not setup or direnv allow has not been run:
WARN[0000] The "HOME_IPC" variable is not set. Defaulting to a blank string.
If you get IPC errors with Cardano node then delete the stale
socket file: rm ~/ipc/node.socket and restart.
If you encounter this message on the midnight node it's likely that the cardano-node is still syncing and it will go away once it's fully synced:
Unable to author block in slot. Failure creating inherent data provider:
'No latest block on chain.' not found.
Possible causes: main chain follower configuration error, db-sync not synced fully,
or data not set on the main chain.
Apache 2.0. PRs welcome, please see CONTRIBUTING.md for details.