Skip to content

docker.md

Latest commit

 

History

History
75 lines (57 loc) · 1.99 KB

docker.md

File metadata and controls

75 lines (57 loc) · 1.99 KB

Docker

Building

Images are built per environment using Nix. Each image has the matching config/{env}.yaml and Cardano network config baked in — only secrets need to be supplied at runtime via environment variables.

nix build .#docker-dev
nix build .#docker-staging
nix build .#docker-prod

Load the resulting image into Docker:

docker load < result

Running locally

Prerequisites

  • A running Cardano node (see nix run .#cardano-node-preprod)
  • A running PostgreSQL instance (see nix run .#postgres)
  • An .env.local file with secrets (see below)

.env.local

Secrets and any local overrides are passed via --env-file. The required database credentials follow the standard HOARD__* naming convention (see configuration.md):

HOARD__DATABASE__USERS__READER__USER=hoard_reader
HOARD__DATABASE__USERS__READER__PASSWORD=...
HOARD__DATABASE__USERS__WRITER__USER=hoard_writer
HOARD__DATABASE__USERS__WRITER__PASSWORD=...

Run command

The local PostgreSQL instance uses a Unix socket (no TCP, no password). Mount both the node socket and the PostgreSQL socket directory into the container, and use --network=host so the container can reach any TCP services on the host:

docker run --rm \
  --env-file .env.local \
  --network=host \
  -v $(pwd)/data/node:/app/data/node \
  -v $(pwd)/data/postgres:/app/data/postgres \
  cardano-hoarding-node:dev
Mount Purpose
data/node Cardano node Unix socket (data/node/preprod/node.socket)
data/postgres PostgreSQL Unix socket directory

Deployment (ECS)

In ECS, both the Cardano node socket and the database are reached over the network, so no volume mounts are needed. Pass secrets as environment variables in the task definition:

HOARD__DATABASE__HOST=<rds-endpoint>
HOARD__DATABASE__USERS__READER__USER=...
HOARD__DATABASE__USERS__READER__PASSWORD=...
HOARD__DATABASE__USERS__WRITER__USER=...
HOARD__DATABASE__USERS__WRITER__PASSWORD=...