I booted up docker images and started invoking postman tests by importing the postman collection as documented in README.md.
There are no logs captured on what went wrong written to docker-compose logs apart from what I see below:
b_1 | 2020-09-18 22:56:22.049 UTC [1] LOG: starting PostgreSQL 12.2 (Debian 12.2-2.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
db_1 | 2020-09-18 22:56:22.050 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
db_1 | 2020-09-18 22:56:22.050 UTC [1] LOG: listening on IPv6 address "::", port 5432
db_1 | 2020-09-18 22:56:22.139 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1 | 2020-09-18 22:56:22.387 UTC [65] LOG: database system was shut down at 2020-09-18 22:56:21 UTC
db_1 | 2020-09-18 22:56:22.520 UTC [1] LOG: database system is ready to accept connections
docker_adr-db-migrate_1 exited with code 0
adr-frontend_1 | (node:1) UnhandledPromiseRejectionWarning: Error: connect EHOSTUNREACH 172.18.0.12:5432
adr-frontend_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1145:16)
adr-frontend_1 | (Use `node --trace-warnings ...` to show where the warning was created)
adr-frontend_1 | (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
adr-frontend_1 | (node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
mock-dh_1 | (node:1) UnhandledPromiseRejectionWarning: Error: getaddrinfo ENOTFOUND db
mock-dh_1 | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:67:26)
mock-dh_1 | (Use `node --trace-warnings ...` to show where the warning was created)
mock-dh_1 | (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
mock-dh_1 | (node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
adr-backend_1 | (node:1) UnhandledPromiseRejectionWarning: Error: connect EHOSTUNREACH 172.18.0.12:5432
adr-backend_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1145:16)
adr-backend_1 | (Use `node --trace-warnings ...` to show where the warning was created)
adr-backend_1 | (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
adr-backend_1 | (node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
adr-backend_1 | (node:1) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
adr-housekeeper_1 | (node:1) UnhandledPromiseRejectionWarning: Error: connect EHOSTUNREACH 172.18.0.12:5432
adr-housekeeper_1 | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1145:16)
adr-housekeeper_1 | (Use `node --trace-warnings ...` to show where the warning was created)
adr-housekeeper_1 | (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
adr-housekeeper_1 | (node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
adr-housekeeper_1 | (node:1) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
mock-register_1 | WARNING: x-forwarded-proto header not detected for an https issuer, you must configure your ssl offloading proxy and the provider, see documentation for more details: https://github.com/panva/node-oidc-provider/tree/v6.29.3/docs/README.md#trusting-tls-offloading-proxies