The Cadence container starts up faster than the Postgres container it depends on when launched through a Docker Compose stack normally. Since Cadence does a bunch of database configuration on initial connect, we end up without a working database.

We alleviate this currently with a hardcoded wait time before initial connect.

A more precise method (maybe timed auto-retry through Compose or in code) would be better.