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.94.1:
docker pull ghcr.io/blinklabs-io/dingo:0.94.1Start 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 \ --env DINGO_METRICS_BIND_ADDR=0.0.0.0 \ --volume dingo-preview-data:/data/db \ ghcr.io/blinklabs-io/dingo:0.94.1Port 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. The image keeps metrics on container loopback by default, so the
DINGO_METRICS_BIND_ADDR=0.0.0.0 override makes the published metrics port
reachable from the host while the host side remains local to 127.0.0.1. 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.94.1 \ --config /tmp/dingo.yaml serveIf the custom configuration publishes the metrics port, set
metricsBindAddr: "0.0.0.0" in dingo.yaml or set
DINGO_METRICS_BIND_ADDR=0.0.0.0 in the container environment. Mounting a
configuration file alone does not make loopback metrics reachable through a
published port.
The 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.
The image already prepares a snapshot directory under its /data/db volume
for UID:GID 1000:1000. When databaseLifecycle.snapshotDir points to a
separate host bind mount, set that host directory’s ownership to UID:GID
1000:1000 and prepare it before starting Dingo. Otherwise, Dingo fails
startup with a writability or permission error.
Configure published metrics
Section titled “Configure published metrics”The node and Mithril metrics endpoints accept anonymous requests. Use the bind address and host port mapping shown above to keep metrics reachable only from the host.
The metrics endpoints use plain HTTP. Apply network-level controls when exposing them beyond a trusted network.
Append to an existing log file
Section titled “Append to an existing log file”Set DINGO_LOG_FILE together with DINGO_LOG_FILE_APPEND=true to reuse a log
file across container restarts:
docker run --detach --name dingo-logged \ --env DINGO_LOG_FILE=/tmp/dingo.log \ --env DINGO_LOG_FILE_APPEND=true \ ghcr.io/blinklabs-io/dingo:0.94.1Append mode activates only when DINGO_LOG_FILE_APPEND equals the exact string
true. Dingo appends to an existing regular file, creates the file when it is
missing, preserves existing permissions, and inserts a newline before new
output when the final line has no newline. Dingo rejects symlinks and
non-regular files. When DINGO_LOG_FILE_APPEND is unset or has any other
value, DINGO_LOG_FILE must name a new file.
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