pepper-agent

pepper-agent initializes and runs a Pepper node, or creates an offline metadata backup.

Synopsis

pepper-agent [--config PATH] [COMMAND]

Global options

--config <PATH>

Configuration file. Defaults to ./pepper.toml when present, otherwise /etc/pepper/pepper.toml.

-h, --help

Print command help.

Run the node

pepper-agent --config /etc/pepper/pepper.toml

With no subcommand, the agent opens storage and metadata, starts the authenticated QUIC listener, starts the loopback HTTP API, recovers jobs, and starts repair tasks. Stop it with SIGINT/Ctrl-C.

init

pepper-agent init [--config PATH]

Loads and validates an existing configuration, creates data and storage directories, generates the node identity when allowed, and initializes redb metadata. It does not generate a configuration file.

backup

pepper-agent backup --output <PATH> [--config PATH]

Copies metadata.redb to PATH. Stop or quiesce the agent first; the command requires exclusive access to the metadata database. Parent directories are created when necessary.

Environment

RUST_LOG

Tracing filter, for example pepper_agent=debug or info.

PEPPER_FIRECRACKER_KERNEL_IMAGE

Guest kernel override used when compute.firecracker_kernel_image is absent.

Files and endpoints

<data.path>/node.key — Ed25519 node identity unless identity.key_path overrides it.
<data.path>/metadata.redb — local metadata database.
GET /healthz and GET /metrics — local health and Prometheus-style metrics.
The HTTP API is loopback-only and optionally requires auth.api_bearer_token.