Minimal reproduction of the problem with instructions
When I push my container up to Google Cloud, and Cloud Run tries to run my container, and I get this error in Google Cloud logs when db-migrate is run from my container
(NOTE: I replaced the real IP for the DB with X's for this post to hide it here)
I saw that there was in the past in one of the issues a acquireTimeout database prop the creator of db-migrate suggested but I tried that and I don't see that in the docs so I don't know that it's a thing anymore. If not a thing I'm not sure how to add a timeout for db-migrate.
Environment
db-migrate version: ^0.11.13
plugins with versions: "^1.2.2"
db-migrate driver with versions: PostgreSQL 12.12
Additional information:
Node version: 18.x
Platform: Linux via node:18.1.0-alpine docker image
I'm submitting a...
Current behavior
I am running the following in my Docker Container:
Expected behavior
After container runs my db-migrate command, it's able to connect to the database without timing out.
Dockerfile
...some stuff and then:
CMD [ "node_modules/db-migrate/bin/db-migrate", "up:production", "-e", "production" ]
Minimal reproduction of the problem with instructions
When I push my container up to Google Cloud, and Cloud Run tries to run my container, and I get this error in Google Cloud logs when db-migrate is run from my container
(NOTE: I replaced the real IP for the DB with X's for this post to hide it here)
I saw that there was in the past in one of the issues a
acquireTimeout
database prop the creator of db-migrate suggested but I tried that and I don't see that in the docs so I don't know that it's a thing anymore. If not a thing I'm not sure how to add a timeout for db-migrate.Environment
db-migrate version:
^0.11.13
plugins with versions:"^1.2.2"
db-migrate driver with versions:PostgreSQL 12.12
Additional information:
18.x
Linux
vianode:18.1.0-alpine
docker image