ceremonyclient/docker
2025-12-26 21:20:50 +00:00
..
.dockerignore chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00
.env.example chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00
docker-compose.yml chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00
Dockerfile.release chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00
Dockerfile.source chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00
Dockerfile.source.dockerignore chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00
Dockerfile.sourceavx512 chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00
README.md fix: remove additional comments 2025-12-26 21:20:50 +00:00
rustup-init.sh v1.4.19 2024-06-08 11:32:45 +00:00
Taskfile.yaml chore: consolidate docker files and refine documentation 2025-12-25 15:56:20 +00:00

Quilibrium Docker Guide

This folder contains all the necessary files to build and run Quilibrium nodes using Docker.

1. System Preparation

For system preparation follow this guide.

If you have issues with connecting to others consider opening up additonal ports 50000+ and 60000+

2. Configuration

Configuration Directory

By default, the Docker configuration uses the .config directory at the root of the repository (../.config). This allows you to share configuration between native and containerized builds.

Generating Config

task config:gen

This will generate the configuration in ../.config.

3. Running a Node

Quick Start (Docker Compose)

task up

Or:

docker compose up -d

New Instance

If you are starting a brand new node, a .config/ folder will be created at the repository root.

Important

Once the node is running (the task node-info command shows a balance), make sure you backup config.yml and keys.yml.

Restore Previous Instance

  1. Ensure your config.yml and keys.yml are in the .config/ folder at the repository root.
  2. Start the node: task up