You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first, thank you for this useful library. Though I think I would not be able to use it because our CI environment executes jobs inside docker. When the jest tests are starting, the process gets locked waiting for the DB to start (in my local environment it works perfectly), I've increased the timeout for the wait DB up to 200 seconds without any success. I've the feeling that as this is running in a docker-in-docker context, the port binding would not be performed against my container itself but to the docker host. Is this correct? It there any workaround?
I was thinking that an option to point directly to the container IP, instead of mapping the port would be very useful for this use case.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
first, thank you for this useful library. Though I think I would not be able to use it because our CI environment executes jobs inside docker. When the jest tests are starting, the process gets locked waiting for the DB to start (in my local environment it works perfectly), I've increased the timeout for the wait DB up to 200 seconds without any success. I've the feeling that as this is running in a docker-in-docker context, the port binding would not be performed against my container itself but to the docker host. Is this correct? It there any workaround?
I was thinking that an option to point directly to the container IP, instead of mapping the port would be very useful for this use case.
Thanks!
The text was updated successfully, but these errors were encountered: