Repository navigation
Testcontainers fail health checks when running with Kiri #42
Replies: 2 comments
|
Hello @realonbebeto sorry for all the troubles. |
|
Thanks for the detailed report, @realonbebeto, and sorry for the wait. I ran your exact One thing I did hit, on Kiri and on plain Docker alike: Postgres prints "database system is ready to accept connections" twice. First it prints it on stdout from a short-lived setup server, then on stderr from the real one. Waiting for the stdout line means a test can connect while Postgres is restarting, and the login fails. This change fixed it in every run: .with_wait_for(WaitFor::message_on_stderr("database system is ready to accept connections"))If you still see the unhealthy error after that, could you share your Kiri version ( |
Uh oh!
There was an error while loading. Please reload this page.
Hello @libracoder,
I've noticed that my Testcontainers tests run successfully with both OrbStack and Docker Desktop, but fail with Kiri due to container health checks reporting an unhealthy status.
For context, here's how I'm configuring my PostgreSQL container using
testcontainers-rs:The same configuration works without issues on OrbStack and Docker Desktop.
All reactions