Run Dingo in a Container
このコンテンツはまだ日本語に翻訳されていません。
Dingo publishes container images to GitHub Container Registry. The versioned
image tag omits the leading v from the matching Dingo release tag. This
example uses Dingo v0.81.0:
docker pull ghcr.io/blinklabs-io/dingo:0.81.0Start a Preview node
Section titled “Start a Preview node”The image defaults to the serve command, the Preview network, and the
database directory /data/db. A named volume preserves the database when the
container is stopped or replaced.
docker run --detach --name dingo-preview \ --publish 3001:3001 \ --publish 127.0.0.1:12798:12798 \ --publish 127.0.0.1:12799:12799 \ --volume dingo-preview-data:/data/db \ ghcr.io/blinklabs-io/dingo:0.81.0Port 3001 accepts Ouroboros node-to-node connections. Metrics on 12798 and
the health endpoint on 12799 are published on the host loopback interface in
this example. Keep a separate named volume for each network.
For Preprod, add --env CARDANO_NETWORK=preprod and use a volume such as
dingo-preprod-data.
Use a configuration file
Section titled “Use a configuration file”Mount a readable dingo.yaml and pass its path before the serve command:
docker run --detach --name dingo-custom \ --publish 3001:3001 \ --volume dingo-custom-data:/data/db \ --mount type=bind,source="$(pwd)/dingo.yaml",target=/tmp/dingo.yaml,readonly \ ghcr.io/blinklabs-io/dingo:0.81.0 \ --config /tmp/dingo.yaml serveThe container runs as UID 1000. Make sure a bind-mounted configuration file
is readable by that user. For other node settings, see configuration and
storage modes.
Check and manage the container
Section titled “Check and manage the container”docker logs --follow dingo-previewdocker stop dingo-previewdocker start dingo-previewThe image health check calls /health, which reports liveness and includes
event-loop responsiveness. A healthy container may still be syncing. The
/readyz endpoint is the readiness check: it requires the tip-gap and database
readiness checks to pass, and a block-producer deployment also requires a
running forger with usable credentials. Use /readyz when deciding whether to
route application traffic.
See bootstrap and data
maintenance for Mithril
bootstrap and database operations.
Docs authored by Doc Holiday